chest: global network limit, rework provider

The chest has the "provider" limit setting that prevents it from sending items to the network if there are too many already in the network.
That's great, but it can be tedious to properly set each chest with the same limit.
I'd love a global limit on the number of items that the item network can hold.
Defaults could be "unlimited".
I'd like an easy way to, say, limit iron ore to 10K or plastic to 3K without tracking down and changing a bunch of chests.
Perhaps that could be added to the network item GUI. That currently shows the number of items.
Maybe clicking on an item can pop up a config dialog to allow setting a limit.
Maybe two numbers (current and limit) could be displayed over the icon or the format could be changed to a list.
A request chest would still try to adjust the number of items to that number by sending or taking items. That is what it currently does. (no change to requests).
A provider would hold that many items locally and send excess to the item network.
In other words, send to the item network if there are more than X items in the chest, where X defaults to 0 for each item.
The item network will refuse to accept items that would put it above the limit. (within reason)
The per-chest limit would not be used.
That's a flip of what it currently does.
I'm not sure how to tell the engine that the chest is "full" to not accept more of an item.

I like this. I'm going to play around with some implementations and see where it goes.

I agree setting global provider limits can save time during the initial setup of provider chests, as well as have it easier to adjust the limit afterwards. Otherwise you would have to adjust each chest individually.
One important thing though is, that the individual provider chest needs to retain the ability to overwrite the limit for itself.
For example:
Set the global limit for what your main producers store in the network.
Set the limit individually for each provider chest, that has the same item as a byproduct, so that it does not stall it's main product.

I implemented something along these lines for Network Tanks when they are configured as a Provider. They will send all contained fluids to the network up to a certain limit.
Something like that could be nice for chests, but I also want to play around with the idea of setting default buffers and limits for a specific item across all chests as a way to more flexibly manage resources.
I'm also playing around with the idea of a dynamic chest that can automatically determine buffer and limit based on usage, but that's fairly complex and hard to tune so not sure if I can figure it out.

I'm also playing around with the idea of a dynamic chest that can automatically determine buffer and limit based on usage, but that's fairly complex and hard to tune so not sure if I can figure it out.

I played with adding automatic adjustments to the request buffer.
This change in the 'take' branch of update_network_chest seems to work OK.
      if n_transfer > 0 then
        status = GlobalState.UPDATE_STATUS.UPDATED
        contents[request.item] = current_count + n_transfer
        GlobalState.set_item_count(request.item, network_count - n_transfer)
        -- if we transferred a full buffer and there is enough for another
        -- in the network, then the bottleneck might be in the request buffer,
        -- so up it by 1.
        if n_transfer == request.buffer and network_count > request.buffer then
          request.buffer = request.buffer + 1
        end
      end

It settled out at a little over the stack size of the inserter in some testing.

I spent some time thinking about and tinkering with this.
I came up with a slight redesign that is backward compatible and opens the door for less processing.
This design is based on the availability of global limits, which I have implemented in my local copy.
I'm in the process of trying this out. So far, it looks good.
Chests can either be configured or not. They can be locked or not.
In total, there are four states:

unconfigured, unlocked
unconfigured, locked
configured, unlocked
configured, locked

state: Unconfigured Unlocked
No requests. No filters. No bar.
On each service, the inventory is cleared and everything is sent to the network, up to the global limit.
Items in the chest are tracked (recent_items).
If the global limit is hit (the chest is not empty after being serviced), then it becomes locked.
Excess items are returned to the inventory when it becomes locked.
state: Unconfigured Locked
No requests.
One filtered slot for each recent item that we don't have. Bar is set just above the filtered slots.
Remaining items are placed at/after the bar.
On each service, everything is sent to the network, up to the global limit.
If the chest is empty after being services, it becomes unlocked.
If the item names contained in the chest changes, then the chest is re-locked.
Re-locking pulls everything out of the chest, sets the filters, inserts the items and then sets the bar.
state: Configured Unlocked
No filters. No bar.
On each service:

any items above the buffer level are sent to the network, up to the global limit. If an item fails to send, it is added to the "locked_items" table.
"take" requests are processes as usual
If there are any locked_items (unable to push an item to the net), then the chest becomes locked.

state: Configured Locked
Filters are set for each "take" request, enough to hold the buffer.
Filters are set for each "give" request, enough to hold the buffer.
A single filter slot is set up for each recent item that isn't covered by the above.
The "give" requests are split. Those that can still feed the network are below the bar. Those that cannot are at/above the bar.
Same as today.
On each service, the same processing is done as the unlocked chest.

any items above the buffer level are sent to the network, up to the global limit. If an item fails to send, it is added to the "locked_items" table.
"take" requests are processes as usual
If the locked_items table is empty, then the chest becomes unlocked.
If the locked_items table changes, then the table is re-locked.
Otherwise, no change.

Don't Reset the Chest Inventory
The key improvement is that the chest inventory is re-arranged only when transitioning states and re-locking.
That should be fairly rare.
Leftovers
A locked chest will have at least 1 item it should, but cannot send to the network.
Default Provider Configuration
All unconfigured items effectively have a default "give" request with buffer=0 and limit=0.
limit=0 means use the global limit.
The global limit is used to determine if the item can be sent.
Configured Provider
Configured "providers" behave differently.
They will hold on to "buffer" items before sending to the network.
If limit=0, then the global limit is used.
If limit >0, then that limit is used, allowing a back-door to add more that the global limit to the network.
The current behavior is to send to the network until it is full and then hold onto items.
Configured Requester
Configured "requesters" behave differently in one corner case.
If there are more items in the chest than the buffer value, then the excess is sent to the network without checking limits.
Otherwise, the requesters behave the same.
Anyway, I plan on working out the kinks and posting the code.
I'm hoping this will be much more efficient.

Thanks for the detailed writeup. I'm trying to understand how this works and have a few questions.

Is this still a Network Chest or is this a new type of chest?
Do chests in this configuration allow for a single iron plate to be buffered and prevent more plates from being inserted?
Is there risk that, under high volume conditions, chests shift between locked <-> unlocked in such a pattern that they have lower throughput than if the chest was configured to a fixed value?

Related, but I've been thinking of adding a High Volume Network Chest with many of the benefits you've listed here. These chests have the following properties:

Each HVNC either requests or provides a single item. The buffer and limit values are shared globally between all chests for that item.
The buffer rounds up to the nearest stack size so these chests don't need fancy logic for setting the bar when the buffer is full.
Since HVNCs will update much faster than normal chests, some logic could be added to update 2 or 3 for every normal Network Chest.
HVNCs can have a large number of slots. 100 maybe?

I'm curious if there is some overlap between these two ideas. Maybe some way to take the simplicity that comes from a single item per chest with the dynamic slot counts in your proposed chest?

Is this still a Network Chest or is this a new type of chest?

It is still a network chest.
The main play difference is that 99% of the time, I only have to worry about setting up requests (copied from assembler) and
messing with the global limit.  I found that I don't need to click on the chest hardly ever.
The exception is that I still need to manually set requests to supply furnaces, which can't copy the recipe.
I like it.

Do chests in this configuration allow for a single iron plate to be buffered and prevent more plates from being inserted?

Yes. Pretty much the same as what you did.

If the global limit for iron-plates is set to 2000
and the current network count is >= 2000
and the chest attempts to send an iron-plate
then the chest will become locked (if it isn't already locked)

If that chest has only contained iron-plate, then the locked chest will consist of bar=1 with the excess iron-plate items in the chest.
No filters.
If the chest also once contained, say, copper-plate, the it would set slot1 filtered to copper-plate, the bar=2 and the iron-plate beyond that.

Is there risk that, under high volume conditions, chests shift between locked <-> unlocked in such a pattern that they have lower throughput than if the chest was configured to a fixed value?

I don't think so.
The locking prevents more items from being added to the chest. The chest is still serviced as normal.
What we gain is we aren't resetting the chest on every tick.
If we are at the edge of network capacity and toggling between locked an unlocked often, we'd still be better off.  There are generally several ticks between the state transitions.
For a complex example (mentioned above), suppose I have an unconfigured chest that is supplying both iron-plate and copper-plate. There is a furnace on each side.
When unlocked, the bar is not set and there are no filters.
If the network fills with iron-plates, then we need to stop accepting iron-plates, but keep on accepting copper-plates.
So, slot1 has a filter for copper-plates and the bar is set to 2. Excess iron-plates are at slot 2 and beyond.
That allows the chest to continue to provide copper plates.
[Side note: we could track the maximum amount of items we moved in a single tick and reserve multiple slots for an item. But I've not run into a situation that would require more than 1 slot.]
Eventually, the net can't accept any more copper-plates. At that point, the list of items in the chest changes from just iron-plate to iron-plate + copper-plate. The chest is then "relocked". Since there are no recent items that we don't have, the bar is set to 1 and excess items are beyond.
Suppose that the iron-plate limit is increased or something used iron-plates such that there is space in the net again.
The excess iron-plates are sent and the remaining inventory becomes just 'copper-plate'. Since the items changed, the chest is re-locked.  Slot 1 is filtered for iron-plate and the bar is set to 2. Copper is in slots 2+.
If we service again and send everything to the net, then the filter is cleared and the bar is reset. At that point, the chest is "unlocked" again.
As for the HVNCs, I'm not sure what the buys us, other than configuration simplicity.
Assuming we have 4 loaders pointing at a chest, all sending 360 items/sec (I remember reading that might be possible). That's 1440 items / sec that we have to dispose of. If evenly distributed, that is 24 items/tick.
Assuming iron-ore, which has a stack size of 50, we would need (1440/50) 29 slots to hold all that if we service the chest at 1 Hz.
We process 20 chests/tick @ 60 ticks per second, so, with the current code, we would hit 1 Hz with 1200 chests.
With the dual-queue patch I just sent, if the chest sends some items on each service, it would be on the "active" queue and would be serviced much more frequently.
The number of entities on that list will be short.

One more comment on HVNCs.
A normal chest could be a HVNC if the buffer size for every request is a multiple of the stack size.
Then you could set the filters once and be done. Never have to change them again.
That would be neat and simplify the logic.

Sounds like this addresses the two biggest issues with this mod, usability and performance. I want to figure out how to add these features to the mod in a way that's somewhat backwards compatible, easy enough for users to understand, and simple enough for me to maintain.
If there's a way to add that functionality to a normal Network Chest then that's great, but my guess is that we'll have to make a new type of chest for this functionality.

I found that I don't need to click on the chest hardly ever.

This is a huge improvement over the current implementation. Exciting!

But I've not run into a situation that would require more than 1 slot.

I haven't either but there definitely other factories people have built with 5k+ Network Chests that transfer huge amounts of items.

A normal chest could be a HVNC if the buffer size for every request is a multiple of the stack size.

That's definitely possible but I want to avoid cluttering the existing UI too much, and an easy way to do that is to make a new type of chest.

I'm thinking about implementing this with 3 new chest types, a High Volume Network Requester Chest, and a High Volume Network Provider Chest, and a Network Trash Chest.
HV Requesters can be configured 99% of the time by shift-clicking from an assembler. They don't need any filter slots or bars, and they by default just pull items from the network. These chests will dynamically update the number of items they request (the buffer) based on usage, and this shouldn't be global because different productions need different amounts of items.
HV Providers won't need to be configured 99% of the time. These will use your filter + bar + empty slot approach to detect which items should be sent to the network. The buffer size on these items will be dynamic and the limit will be globally shared for that item type. The buffer size will always be rounded up to the nearest stack so users will have to use normal Network Chests if they want to buffer less than a stack of items.
The third type of chest is a Network Trash Chest that simply sends all items into the network and is useful for recipe side products.
With these 3 chest types, It seems like there's a way to meet the needs for almost any recipe without having to manually select items. Additionally, these new chest types can be updated much more efficiently than Network Chests which opens the door to optimizations.
What do you think?

Also since this is a big feature, does it make sense for me to make a branch dedicated to this work and give you push access? That should hopefully make it easier to reduce merge conflicts and move faster without affecting regular releases.

Just to check my understanding...

HV Requesters
That would be like a Logistic Requester chest, correct?
It never removes items from the chest, but only tries to request items based on the configured level.  It does not have a "limit" to prioritize requests.
And if you fill the chest with junk then add a new request... tough luck?
Or would it 'trash" anything that it wasn't requesting?
I'd love the UI to look like a Logistic Requester chest, if possible.
Including the inventory view with all the stack manipulation clicks.

HV Providers
This would be an "unconfigured" chest with the locked/unlocked state.
It would respect global limits.

Network Trash Chest
I'm assuming this would ignore global limits and just send everything.

That all sounds good.

Also since this is a big feature, does it make sense for me to make a branch dedicated to this work and give you push access? That should hopefully make it easier to reduce merge conflicts and move faster without affecting regular releases.

Yes, that would make sense.

Sounds good. I made the branch high-volume-chests to start on this, and once it's done it can be merged into main.
Yeah HV Requesters are like Logistic Requester chests except HV Requesters don't have a number since that number will be determined automatically (or defined globally if automatic is too hard).
 Maybe we can add logic to auto-trash unrequested types of items but I don't think this case can occur accidentally.

The only extra part I'll add is that I'm hoping these new chest types can be efficient enough that we can update a few of them for the same cost as updating a single Network Chest which should increase factory throughput dramatically. Long-term, I see endgame factory setups as having a mall filled with low-throughput network chests while the rest of the factory uses efficient HV chests.


Add snap function to scene view

Is your feature request related to a problem? Please describe.
When planning the layout of a game there are times, when certain scenes should align to make it easier to comprehend.
Describe the solution you'd like
Adding the possibility to snap scenes to an underlying grid would make it a lot easier to make a clean project, especially when you have to move scenes around.
Describe alternatives you've considered
A button that can be pressed to align two maps would also help, but not as much

Forgot to mention that it would be great if the snapping was optional. You could add a check box at the top left of the scene view to enable/disable it. Being able to choose the grid size would be nice as well.

Forgot to mention that it would be great if the snapping was optional. You could add a check box at the top left of the scene view to enable/disable it. Being able to choose the grid size would be nice as well.

The check box should be in the View menu. Otherwise I totally agree with you. I’d really like this feature


[BUG] comments fail to load

Duplicate of issue #356 but unfortunately there have been no new releases despite it being fixed 5 months ago.

v2.16.3 android 12.

Also happens on v3.0.0-beta1

Please could someone in the thread provide a link to a tweet or thread that reproduces this error? I was seeing this error on threads that contained deleted tweets, which is fixed now, but I need a bit of help finding what's causing it for you all.

I have a few examples in #356.

@geominorai all the tweets in #356 are now working - they were all deleted tweets 🙂 or if you're still seeing it in 3.0.0-beta1, please let me know.
I think @kvnvallis might be seeing a different error, or the same error but caused by a different tweet.

Sorry, v3.0.0-beta1 works fine, the issue is resolved. I thought i had installed it but i was still using 2.16.3

I get an "App not installed" error when I try installing the beta, so I cannot test this. Uninstalling the old version first did not seem to help.

@geominorai @fusionneur that usually happens when the app is installed from a different source (e.g. F-Droid), as its signed with a different key. You'll need to uninstall the app, including from any other profiles (like a Work profile, or Shelter profile), then install it from GitHub. Or wait for the beta to come through to F-Droid in a few days.
I know it's annoying, but it's an Android limitation :(

Closing, as this appears fixed now.

Thanks, it installed after I found and cleared the old versions out of all profiles.
I can confirm the patch works on the previously mentioned Twitter comments!


Update schemavalidator.md

Fixing BTARN SDK path

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-rosettanet/schemavalidator.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat(documentation): add form-check stories

Preview environments are getting posted here, as soon as they are ready!


Do not respect global scopes in the bread

I believe an admin panel should not obey global scopes. This commit will make the VoyagerBreadController discard the filters imposed by global scopes using "withoutGlobalScopes" and "newQueryWithoutScopes".

bump.. ?

This is definitely a breaking change as some people may be using global scopes and end up having to rewrite everything to Policies.
At least for 1.0.x

Agreed. I should probably add it as an option in the BREAD builder instead.

Make it either a config var, or take a look at #2827
It introduces a new details column to Data-Types with which you could implement a var respect_global_scopes or so


About the config yaml of CTW1500 dataset

I ran the total-text and the results were good, so I would like to try the CTW1500 dataset. Could you please provide the config yaml for CTW1500, thanks.

Thank you for your attention. You can directly use the total-text config by changing the size of the test image to (704, 1056). We will release the config for the v2 version of CTW1500 in the future.


@Nirajn2311 Is there no way to flag a post like on the forum?

@randelldawson there is no way to flag or remove a issue here as far as I know.


Docs behind proxy

Context

hapi-swgger version: 7.4.0

What are you trying to achieve or the steps to reproduce ?
I have set configuration base pathh. basePath: /demo/api/
What result did you get?
swagger-ui gets a lot of 404 errors complaining about links missing. All js and css links and hrefs dont include basePath set in conf (still "/swaggerui/.....)
What did you expect ?
js and css links should include basePath.
Thanks
Indrek

Hi @glennjones I'll verify this PR tomorrow and let you know if it works on my machine.

@danactive @indreek any progress here? I really need it :-)

@ns3777k No I changed priorities at work, so I haven't verified this PR yet. I still need this feature though

@danactive I also really need it.

@danactive plz verify PR soon. I wish this feature will be in next release.

Hi. I would also like to have this feature very much. Is there, by any chance, a way to simply add
<base href="${hapiSwagger.basePath}" />
to the <head> of Swagger HTML file?
This should solve the issue pretty nicely.

@indreek I had a look at this and deployed it behind a reverse proxy of our own; lgtm.
Since our service also hosts the swagger docs this PR works fine as is. For setups involving swagger docs and API being served separately we might be better off specifying full paths to both API and swagger docs, respectively.

Any progress on this?

I think this can be closed since userland has full control over the html pages needed for swagger ui.


Support generating PowerPC64LE toolchain.

Generates a tar.gz for PowerPC.

@microsoft-github-policy-service agree


Bugfix sizestackorder

Codecov Report

Merging #25 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #25   +/-   ##
=======================================
  Coverage   96.84%   96.84%
=======================================
  Files           9        9
  Lines         792      792
=======================================
  Hits          767      767
  Misses         25       25

Impacted Files
Coverage Δ

src/mutation/size.jl
97.74% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab011dc...b78f8dd. Read the comment docs.


Axios not working with Create React App

Summary
I am trying to get started with Axios in a Create React App. I have used both extensively. However, when I download Axios, it breaks npm start. This is a log of the terminal for you to see. As you can see, npm start was working until Axios was installed. I have done zero coding in this. You can see the commit where this is happening here.
Also, thank you very much in advance for your help! I use Axios all the time and it is really amazing.
Compiled successfully!

You can now view code in the browser.

  Local:            http://localhost:3000/
  On Your Network:  http://<IP_ADDRESS>:3000/

Note that the development build is not optimized.
To create a production build, use yarn build.

^C
jen ~/dev/continuingEd/7_31_17_React_Talk_Jest/code on master[!]
$ npm install --save axios
npm WARN gentlyRm not removing /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/html-minifier/node_modules/.bin/uglifyjs as it wasn't installed by /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/html-minifier/node_modules/uglify-js
npm WARN gentlyRm not removing /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/caniuse-api/node_modules/.bin/browserslist as it wasn't installed by /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/caniuse-api/node_modules/browserslist
npm WARN gentlyRm not removing /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/acorn-globals/node_modules/.bin/acorn as it wasn't installed by /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/acorn-globals/node_modules/acorn
npm WARN gentlyRm not removing /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/acorn-dynamic-import/node_modules/.bin/acorn as it wasn't installed by /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code/node_modules/acorn-dynamic-import/node_modules/acorn
npm notice created a lockfile as package-lock.json. You should commit this file.
added 2 packages, removed 1171 packages and updated 3 packages in 33.755s

jen ~/dev/continuingEd/7_31_17_React_Talk_Jest/code on master[!?]
$ npm start

><EMAIL_ADDRESS>start /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code
> react-scripts start

sh: react-scripts: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/jen/.npm/_logs/2017-07-23T20_54_00_407Z-debug.log
jen ~/dev/continuingEd/7_31_17_React_Talk_Jest/code on master[!?]
$ npm i --save
removed 96 packages in 24.292s
jen ~/dev/continuingEd/7_31_17_React_Talk_Jest/code on master[!?]
$ npm start

><EMAIL_ADDRESS>start /Users/jen/dev/continuingEd/7_31_17_React_Talk_Jest/code
> react-scripts start

sh: react-scripts: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/jen/.npm/_logs/2017-07-23T20_54_37_218Z-debug.log
jen ~/dev/continuingEd/7_31_17_React_Talk_Jest/code on master[!?]
$

Context

Environment: e.g.: npm v5.0.0

Encountered the same with react-boilerplate. Just installing the axios library results in errors. I need to run build again in react-boilerplate to get started.

On my side I can run axios without issues in create-react-app.
Sometimes this kind of issues can be solved by a simple :
rm -Rf node_modules
npm install
Also make sure that you have the latest npm version.

Thank you! I was working with NPM version 5.0.0. However, now that I upgraded to NPM version 5.3.0 it is fixed.

removing and reinstalling the npm packages worked perfectly

you shouldn't have to do this. Does anybody release quality code?


test error

when i test only one image using your trained model,something wrong at
Predicting...
Traceback (most recent call last):
File "test.py", line 29, in
outputs = network.predict(x)
File "/home/dingyuyang/EDSR-Tensorflow-master/model.py", line 172, in predict
return self.sess.run(self.out,feed_dict={self.input:x})
File "/home/dingyuyang/.conda/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 929, in run
run_metadata_ptr)
File "/home/dingyuyang/.conda/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1128, in _run
str(subfeed_t.get_shape())))
ValueError: Cannot feed value of shape (50, 50, 3) for Tensor 'Placeholder:0', which has shape '(?, 50, 50, 3)'
can you help me?

you can use:
inputs = np.expand_dims(inputs, 0)
outputs = network.predict(inputs)
to make the shape of inputs is [1, h, w, 3]


Update common.gypi

Fixing the link error on VS 2013
@ingorichter @ficristo Let me know if this change looks good.

I've build with VS2015 and it's fine :+1: :clap:

Thanks @ficristo for testing this out. I am going ahead with the merge as currently master is not broken.


Fix/issue 66 element-did.com not working

Codecov Report

Merging #71 into development will increase coverage by 0.04%.
The diff coverage is 50%.

@@               Coverage Diff               @@
##           development      #71      +/-   ##
===============================================
+ Coverage        33.72%   33.76%   +0.04%
===============================================
  Files              244      244
  Lines             3146     3142       -4
  Branches           214      213       -1
===============================================
  Hits              1061     1061
+ Misses            1973     1970       -3
+ Partials           112      111       -1

Impacted Files
Coverage Δ

...nt-lib/src/adapters/database/ElementRXDBAdapter.js
86.2% <ø> (ø)
:arrow_up:

packages/element-lib/src/sidetree/resolve.js
92.5% <50%> (+8.4%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 56e18fe...23ac77b. Read the comment docs.


Fix key file name not validating with Azure.Identity >= 1.12.0-beta.3

Azure.Identity updated to validate the key path. Credential bridge saves a new guid as the file path, which did not pass the new validation.
https://github.com/Azure/azure-sdk-for-net/pull/44483/files#diff-03a57cc8541a8a2066317dcaa35be537ba806d60fc4d7e1272573de98e4b7757

The same fix was applied in a different PR.
Thank you for the contribution.


Make drep query parser accept zero or more keys

Changelog
- description: |
    The `cardano-cli conway governance query drep-state` and `... drep-stake-distribution` now accept zero or more DRep verification keys, making the help messages correct.
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
This will close #346 .
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] The change log section in the PR description has been filled in
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
round trip tests
integration tests
See Running tests for more details

[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] The changelog section in the PR is updated to describe the change
[ ] Self-reviewed the diff

Beautiful!
cardano-cli conway governance query drep-state --testnet-magic 4
[
  [
    {
      "keyHash": "037ca7363e8c9c7b3391bee7c45eb3222c5a600ddf8e268b0057b3a6"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "058b60ead63f667c0ff5b40e269dd1f05ce3a804256735ad4eddce20"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "20d832cb15463cc7ccfd40e9658c7398148594f81026591968acb4ce"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 112
    }
  ],
  [
    {
      "keyHash": "24a26a091058744472c20178bda9fcf811a5a31824cf0c49a976329f"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "27ac1c7b513e95c3c952a37b46e94216caee6eca050cd00c914e7194"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "33eb0023afe70a59e8c352be620a63d003bed0339a5a3c0c1646854f"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 105
    }
  ],
  [
    {
      "keyHash": "3b5c380f7830a35cda74f0969c3490221c2e548b31872772e00c17b1"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "4e4dba8ccb384ef1f1682b6aefc21d2557699f0c0695d98331900503"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "766df390f4cc2065c5e28ff175d9fc26cefd23124e8070f0e101dd1c"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "83c733e900f1a5ea5879c977c9ee2138abacf5a3b81c0ac8d86d6f0a"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 112
    }
  ],
  [
    {
      "keyHash": "87c1de0f0c1028ae3c8ce482889f17f651a0c2f3b71a63029b05f0f0"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "946f3a739c7fd618795e8d0e896708ed4dc00ed15be6a8b091ac8e40"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "97a993b0c8166aa8c48345be19257a4025ab764c86e799beab15b303"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 105
    }
  ],
  [
    {
      "keyHash": "97a993b0c8166aa8c48345be19257a4025ab764c86e799beab15b304"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 105
    }
  ],
  [
    {
      "keyHash": "9ca61f53d9ab4a652a4c7b9d5b8e21d0409a5aa04ca0eea282eb5b0e"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 113
    }
  ],
  [
    {
      "keyHash": "9f7e0f20f3c644556abcc4263cfe05bfe1bd122da77465eb392f62eb"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 108
    }
  ],
  [
    {
      "keyHash": "a6fb0cc0a14dd67d87c22beecea780019de9dc2be1ed24992bc7c706"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "b2a7f53b1cae7709ea715473bc0e68321bf70407fb7010349e8689dd"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 116
    }
  ],
  [
    {
      "keyHash": "b8580007d8e9b230dc71b161ca15b4d866060cd20b841b6b736033e4"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "bbff55056ad81f6a0d1fb134db09c8cc1ac09de25f2c864f01b80877"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "c4151afe9b5f4395dfa131f002fa760f55e324f50dc7cbd13a900ddf"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 113
    }
  ],
  [
    {
      "keyHash": "c9ff3121d65e945699cb6041ffef13bedd6726eecfdf138e5795e4a1"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 108
    }
  ],
  [
    {
      "keyHash": "cda7cbb5057ab5cab63c4b19866c39abda9908750640e245710646ee"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 107
    }
  ],
  [
    {
      "keyHash": "e4dafd31d35ce543d4442238efe31cc38a2f03fecc1e6bad9ffd7b1c"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 109
    }
  ],
  [
    {
      "keyHash": "e6181717c26e227812db49b14b9114220e313ccc31459c4675d61a34"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ],
  [
    {
      "keyHash": "ec961dd3848d8c6531403145a8a4324d0be60438fe51232c6c087e27"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 104
    }
  ],
  [
    {
      "keyHash": "edddffe8c66db8bd598ec63733531c07fb4d08909ff1b881b42d7f0d"
    },
    {
      "anchor": null,
      "deposit": 0,
      "expiry": 106
    }
  ]
]

Also for drep-stake-distribution
cardano-cli conway governance query drep-stake-distribution --testnet-magic 4
[
    [
        {
            "contents": "058b60ead63f667c0ff5b40e269dd1f05ce3a804256735ad4eddce20",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "766df390f4cc2065c5e28ff175d9fc26cefd23124e8070f0e101dd1c",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "87c1de0f0c1028ae3c8ce482889f17f651a0c2f3b71a63029b05f0f0",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "946f3a739c7fd618795e8d0e896708ed4dc00ed15be6a8b091ac8e40",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "9ca61f53d9ab4a652a4c7b9d5b8e21d0409a5aa04ca0eea282eb5b0e",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "c9ff3121d65e945699cb6041ffef13bedd6726eecfdf138e5795e4a1",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ],
    [
        {
            "contents": "e4dafd31d35ce543d4442238efe31cc38a2f03fecc1e6bad9ffd7b1c",
            "tag": "DRepKeyHash"
        },
<PHONE_NUMBER>
    ]
]


OSM Stats page has to be updated for year 2018

http://www.missingmaps.org/osmstats/

stats page has been redone https://www.missingmaps.org/statistics/


test

Task/Issue URL: https://app.asana.com/0/488551667048375/1202717423070850/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #2147   👈

This comment was auto-generated by Graphite.


cmd/compile: incorrect boolean value passed to function

What version of Go are you using (go version)?
go version go1.8rc2 darwin/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
What did you do?
https://play.golang.org/p/hebuAYQ6eo
Take the program above, that on go 1.7.4 prints out "The right thing.", and run that with a go compiler of version 1.8rc2. You now find that it prints out "The wrong thing." Additionally interesting, if you comment out line 15, the second call to "panicWhen", then the first call behaves correctly.
What did you expect to see?
I expect the program to panic with "The right thing."
What did you see instead?
The first call to panicWhen gets the argument cond as false, and panics with "The wrong thing."

Confirmed. This is a bug that appeared in 1.8.

/cc @randall77 @mdempsky

Nice bug.
And if you delete the dead code line panicWhen(*e == *e), then the bug goes away.

The bug is in nilcheck phase, where there is a NilCheck Op in the same block as IsNonNil and happened to be stored before it (since values are not stored in order, until the scheduling phase). But logically NilCheck is after the IsNonNil.

I think we should explicitly check the memory to set/clear nonNilValues.

If it helps, git-bisect shows the offending commit as: 3134ab3c2d58d2c9f93471c85405cb26ccdf0f4d

@dsnet, yes, that is it. Before that commit, NilCheck always introduces a new block (BlockCheck) which enforces the value ordering. After that, it no longer introduces new block, so NilCheck could affect values in the same block but logically before it.

Not sure where gopherbot is, there's a CL at http://golang.org/cl/35495

Also proposed CLs at https://golang.org/cl/35496 (Cherry's) and https://golang.org/cl/35485 (mine).


Implement tail() for TS objects

tail(ts::TS) should return the last 10 rows of ts.

Completed tail


createPoolLedgerConfig error: PoolLedgerConfigAlreadyExistsError #251

Can someone answer? Sorry, my English is not very good. The following content comes from machine translation. I used von in the node part, and I used nodejs demo from indy-sdk. The result is the following error. I don't know where I am wrong. I will post my error content and von screenshot below

This is Genesis obtained from von. I directly copied it to util.js. The code and von are on the same server

von status

I seem to have made a new mistake
(node:13414) UnhandledPromiseRejectionWarning: ReferenceError: og is not defined

The last problem seems to be negligible, but I don't know how to solve this new problem


Vendor operatorkit updated controller internals

Uses the updated operatorkit internals from https://github.com/giantswarm/operatorkit/pull/338.
I think its good to test these in multiple operators since the changes under the hood are quite big.

Tested on godsmack. I'll merge in the morning.

Take it over from here; merging now.


DbInitializer should get environments as an argument

Instead of having the environments in which the migrations run on startup hardcoded, DbInitializer should receive them as arguments in the constructor, probably in a settings object.

How should we do this? Do we declare the variable in our config? How do we create the settings object?

One of the project's episodes was dedicated to that topic 😆
You can check it out here.
But in summary, yes, we should create a new class to represent the DbInitializer settings, which will probably contain a string[] with the environments. We add it to the appsettings.json file, and in the Startup class we configure it to be used.

Will submit a pull request on what is on my mind on this. .😁

Solved during migration to .NET Core 3.0.


[WIP] Add tests for 'main.js'

Part of https://github.com/actions/create-github-app-token/issues/43
This PR adds tests for main.js, similar to the tests that already exist for post.js.
Specifically, it adds tests that:

Verify main exits with an error when GITHUB_REPOSITORY is missing
Verify main overrides request’s default baseUrl only when GITHUB_API_URL is set

More tests will be added before I promote this PR out of draft.
This PR adds a dev dependency on esmock, which ava (the test runner this project is already using) mentions (recommends?), in “Mocking”. It’s added in order to allow inspection of values passed to lib/main.js’s main. A cursory glance at “Evaluating third party dependencies” on The Hub (only accessible to Hubbers) didn’t turn up any immediate concerns, but I’ll examine esmock more thoroughly before promoting this PR out of draft.

I added a happy path test (that mocks requests and validates stdout), in 43f2499. @gr2m, is that what you had in mind?

Yes, I just looked at it, looks good 👍🏼 Thank you!

This PR is already in draft, but to err on the side of over-communicating: After rebasing, npm test exits with an error. I’m working on debugging that.

🤔 I’m not sure why the test / Integration (pull_request) check is failing; npm test passes on my machine. I wonder if it’s a line-feed character issue?
Excerpt from the logs:
Run npm test

><EMAIL_ADDRESS>test
> ava tests/index.js

  ✔ post-token-unset.test.js (669ms)
  ✔ main-missing-repository.test.js (823ms)
  ✔ main-missing-owner.test.js (1s)
  ✔ post-token-skipped.test.js (1s)
  ✔ post-token-set.test.js (1.2s)
  ✘ [fail]: main-token-get-owner-set-repo-set-to-one.test.js stdout
  ✘ [fail]: main-token-get-owner-set-to-org-repo-unset.test.js stdout
  ✘ [fail]: main-token-get-owner-set-repo-set-to-many.test.js stdout
  ✘ [fail]: main-token-get-owner-set-to-user-repo-unset.test.js stdout
  ✘ [fail]: main-token-get-owner-unset-repo-set.test.js stdout
  ✘ [fail]: main-token-get-owner-unset-repo-unset.test.js stdout
  ─

  main-token-get-owner-set-repo-set-to-one.test.js

  tests/index.js:12

   11:     t.snapshot(stderr, "stderr");
   12:     t.snapshot(stdout, "stdout");
   13:   });

  stdout

  Difference (- actual, + expected):

    `owner and repositories set, creating token for repositories "actions/create-github-app-token" owned by "actions"␊
  - ::add-mask::`
  + ::add-mask::␊
  + ␊
  + ::set-output name=token::␊
  + ::save-state name=token::`

  › file://tests/index.js:12:7

Update: Ah, I now suspect the issue is that @actions/core performs differently in the Actions runner environment, vs locally, i.e. logs different things.

That’s why some projects mock core in their tests, e.g. actions/checkout`.

Ah, no, actually, there’s a subtle bug with the code that returns an installation access token (it’s missing the response header that makes it an object). The runner warns about this; local does not. That’s probably the source of the error.


can't enter numbers beginning with 1 or 2 (maximum open tabs)

I have a wide screen and can probably tolerate 10-15 tabs open at one.   Input should respect human.

Sorry, there was an error in keymap file and those numbers weren't working anywhere


refactor: add transaction query support

What I did

Added num_transactions to ape.api.providers.BlockAPI
Created ape.api.query.BlockTransactionQuery
Added transaction method to ape.api.providers.BlockAPI
Added perform_block_transaction_query to ape.managers.queryDefaultQueryProvider

fixes: #727
How I did it

Followed issue number 727
How to verify it

run pytests
Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

This is very obviously raw, and not ready to be merged, I have a circular import issue here, and would like input on what we should do with BlockAPI having this transaction method added to it.  It causes a circular import.

Another, more meta thought: perhaps QueryManager/QueryAPI subclasses needs to work with sets of iterators returned from .perform_query and .update_cache methods, and let the downstream .query methods instead convert to pd.DataFrame objects, so we don't have all of these conversion back and forth occuring until the data is finally asked for

@unparalleled-js I think we can merge this?

I don't have a test for this yet. I started to make the test, but it's not finished yet.

Very basic test here, BlockTransactionQuery is working as expected. Trying to get this to query through the DefaultQueryProvider at the moment


[QA] Goerli | Block-Fountain: Cubes Move Without Button Press and Board Button Inaction

Explorer Alpha build version:
v0.8.0
Issue Description:
Cubes in the Goerli Block-Fountain scene move without requiring any button press. Additionally, pressing the board button does not trigger any action.
Steps to reproduce:

/goto goerli
Navigate to (79,4) Block-Fountain scene
Observe cubes moving without prior interaction with the board.
Attempt to interact with the board buttons.

Expected behavior:
https://github.com/decentraland/unity-explorer/assets/146741383/9190562c-e90c-401d-976b-7e6923272617
Current behavior:
https://github.com/decentraland/unity-explorer/assets/146741383/58906edc-a522-43f8-986b-41a4afc518d4
Additional Notes:
Windows 11. 12th Gen Intel(R) Core(TM) i7-12650H 2.30 GHz. nvidia geforce RTX
Macbook M1 Pro Sonoma 14.5

With a build from today, I'm not seeing this issue anymore :)


P5.dart

What's the difference between flutter_processing and p5.dart?

I'm not sure. I haven't done a deep dive into that other project. It looks like a similar goal.


Appstudio update test-component-pac-swph

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-swph-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
4 seconds
init

✅ Succeeded
12 seconds
clone-repository

✅ Succeeded
32 seconds
build-container

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
13 seconds
inspect-image

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
9 seconds
optional-label-check

✅ Succeeded
5 seconds
show-summary


Python with Alpine Linux to make the image size smaller?

Is it possible to use Alpine linux to make the image size smaller?

Hello @vagyvin,
In theory, it is possible. However, this would require some dependencies like aws-lambda-ric, and maybe more.
I want to make my Dockerfile as small as possible for an example. So given these considerations, I'm currently not planning to switch to Alpine Linux.


Support for Multiple A Records

Hi,
I'm trying to understand if this client support one record of a broker that contains multiple A records.
Will it work in the same way as it would If I added all the brokers Ip to the brokers array in initialization?
consider: kafka-broker:9092  contain A records  for kafka-broker  1-3
Will:
const kafka = new Kafka({
clientId: 'my-app',
brokers: ['kafka-broker:9092']
})
===
const kafka = new Kafka({
clientId: 'my-app',
brokers: ['kafka-broker-1:9092','kafka-broker-2:9092','kafka-broker-3:9092']
})
Thanks!

@snirad32 it works just fine, these brokers are only used to discover the cluster. We used to use a load balancer instead of providing a list of brokers.

@tulios, I  noticed that this feature is somewhat new this is why i asked:
I mean librdkafka start support it from verision 2.1:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-302+-+Enable+Kafka+clients+to+use+all+DNS+resolved+IP+addresses

let me know if I can be of help

you can point me to the place that needs fixing and I can do it myself if you want :)

Hi @snirad32, you might need a new property to enable this behavior, but I think the change should happen in connection#connect - https://github.com/tulios/kafkajs/blob/master/src/network/connection.js#L97
Another option is to add the information about multiple IPs to the connection and handle the error in the broker#connect - https://github.com/tulios/kafkajs/blob/master/src/broker/index.js#L82

Hey @tulios i believe that it's a very important feature for anyone who's aiming to work with KafkaJS on a large kafka cluster. Could you shed light on if/when do you expect it to be added?
Many Thanks.

Unfortunately we all have jobs and responsibilities outside of KafkaJS, so it's hard to say when exactly any of us will be able to work on an issue that isn't a pressing need for us.
Ultimately, the fastest way to get a certain feature in is to make a pull request implementing it. It's generally easier for us to to make the time to review PRs than create them ourselves, and it creates more of an urgency since we want to be receptive and appreciative of other people's time and contributions.

Hey @unbalanced, I will take a look at it. It shouldn't be too hard to support it.

Is this the
*client.dns.lookup == *use_all_dns_ips
option from the java client?
On Mon, 10 Feb 2020, 17:25 Túlio Ornelas<EMAIL_ADDRESS>wrote:

Hey @unbalanced https://github.com/unbalanced, I will take a look at
it. It shouldn't be too hard to support it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tulios/kafkajs/issues/509?email_source=notifications&email_token=ABDLW5Q7XL35OXD6POWJ5CDRCEMPBA5CNFSM4I2XSUXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELHZM6Y#issuecomment-584029819,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABDLW5R3ZFNIQ4KQOTZS4IDRCEMPBANCNFSM4I2XSUXA
.

Thanks everyone,
@tulios, this is much appreciated.
@Nevon, totally understand! I wanted to see first what's up before I dive in further. Since from a glimpse on the code on master it looked to me as if it should already work. And a simulation I made showed an inconclusive result.

Is this the
client.dns.lookup == use_all_dns_ips
option from the java client?

Yes, correct, that would be the equivalent change. For reference, that was implemented in this PR
for the Java client: https://github.com/apache/kafka/pull/4987
I took a brief look at this this morning, to see if it was a trivial change or not. My assessment is that while it's not huge, it's not that simple. Note that I'm not saying that I'm going to implement this - I'm just sharing what I learned looking through this.
Here's how things currently work:

Connection.connect calls createSocket, passing in on* (onConnect, onError etc.) and is also responsible for enforcing the connection timeout. onError will disconnect, clear queued up requests, abort ongoing authentications and a few other things. When onConnect is called, Connection.connect will resolve.
createSocket simply calls the provided SocketFactory and expects to get a net.Socket back, to which it attaches the on* handlers.
SocketFactory can be passed in from userland to allow people to customize the socket, so we can't really modify what's going on in there, but we know it will receive a host and a port and return a net.Socket instance.
The default SocketFactory that we ship calls net.connect, which is an alias of net.createConnection. What's notable is that if it is called with a hostname rather than an IP address, it will call dns.lookup with hardcoded options that make it resolve to a single IP.

What this means is that we cannot rely on this being handled within net.Socket itself, and since SocketFactory can be injected we cannot solve it in there, which means that it has to be solved either in createSocket or Connection.connect. I.e. we have to resolve the hosts ourselves.
Another interesting thing that we haven't mentioned is dealing with IPs resolving to the same underlying host. For example, if you currently specify localhost as a broker, it will most likely resolve to <IP_ADDRESS>, and we will make a single connection attempt to that IP. If we naively change to using all resolved IP addresses this behavior will change so that we make two connection attempts. Why? Because of multiple IP families:
// Current behavior
dns.lookup('localhost', (err, addr) => console.log(addr))
> <IP_ADDRESS>

// After change
dns.lookup('localhost', { all: true }, (err, addr) => console.log(addr))
> [ { address: '<IP_ADDRESS>', family: 4 }, { address: '::1', family: 6 } ]

The Java client deals with this by taking the first resolved IP family and then filtering out all other resolved IPs that are not of the same family. If you combine this with the verbatim: true option on lookup, we will basically let the DNS server decide if we should use IPv4 or IPv6. I'm not sure what the implications of this are, but it does start to feel like maybe this wouldn't be a completely transparent change.
Another consideration is that using the custom SocketFactory we currently allow users to replace dns.lookup with for example dns.resolve. This can have important consequences, and so I think it's an important capability to retain now that we are lifting DNS resolution up one level. Therefore I'm inclined to say that this should be a top-level option on the client.
new Kafka({
  dns?: {
    all?: boolean, // default false
    lookup?: (hostname: string, options: LookupOptions, callback: (err: Error | null, address: LookupAddress[], family: number) => void): void // default `dns.lookup`
  }
})

My general thinking is that this probably has to be solved within Connection.connect, but that code is currently a little bit hairy, so it's not as straightforward as I would like. Basically, before connecting we'd need to lookup the addresses for the host. If dns.all: false we take addresses.slice(0,1), otherwise the whole lot. We then filter out any addresses other than the one of the first family returned.
On connect, we essentially loop through the addresses and try to connect to each one. Only when we have exhausted all of them do we propagate the error upwards. This means re-writing the error handling as well as the timeout enforcement.


Fix comparison operator bug, and implement minimum working example.

Implement a fix for the comparison operator bug, alongside implementing a bare-bones working example and very brief instructions on how to use.

Ah - I've written a bunch of stuff loosely based on your code; I forked the repository mainly to give you some of the credit for the original ideas. The scientific Python install I've been using in my degree is 2.7, and I plan to stick to that. I think our ideas diverge, so I shan't be submitting any more pull requests - I just had to fix that little bug to get it working correctly and thought since I'd fixed it for you I'd make it easy for you to use it.
I think I'll close this pull request, but you should just fix the three lines which were broken in your original code. I only meant the first commit to be included in the request, but apparently that's not how GitHub sees things (I should have submitted a pull request from another branch) . . .
My code is only loosely based on yours - if you'd rather I made a new repository so that you didn't have my branch; let me know how to credit you, and I'll do that.
As for the str(...) conversion; if you do anything other than dump to JSON, things still go horribly wrong. I had great difficulty getting Python to play nicely with the Unicode nature of BeautifulSoup's strings and my fix was an ugly hack to set Python's default encoding to unicode for only one file:
'''python
reload(sys)
sys.setdefaultencoding('utf8')
'''
which isn't good practice!

did you mean 21-24 of fb_parser.py were the ones I broke?

Whoopsie, yes those were the lines I meant.

As for the str(...) conversion; if you do anything other than dump to JSON, things still go horribly wrong. I had great difficulty getting Python to play nicely with the Unicode nature of BeautifulSoup's strings and part of my fix was an ugly hack to set Python's default encoding to unicode for only one file

Ah yes, that probably has to do with the fact that we're using different versions of python. I believe python 3.X's default encoding is utf-8 to begin with which would explain why str(...) worked for me but not yourself.

That makes sense - you might just want to make sure that it works fine in Python 3 still! It'd be handy if it worked in both!

No that would be too easy. Oh well, everything is fixed now!


New Graphics for Modus

New Modus illustrations needed for:

[ ] Modus homepage header light mode (general https://modus.trimble.com/)
[ ] Modus homepage header dark mode (general https://modus.trimble.com/)

Style guide component introduction pages (dark and light mode):

[ ] Web (x2)
[ ] Mobile (x2)
[ ] In-Field (x2)
[ ] XR (x2)
[ ] Desktop (x2)

Error page graphics:

[ ] Error pages (dark and light)

Figma file header cards:

[ ] Web
[ ] Mobile
[ ] In-Field
[ ] XR
[ ] Desktop
[ ] Foundations
[ ] Iconography

Replace also on the Bootstrap and React-Bootstrap sites

High resolution extracted from Discord
Meeting placeholder with Cory Fri Mar 17th

For the new images I suggest we modify the aspect ratio to work better as Open Graph images (used when sharing on Slack and Google Chat). Right now the images crop too heavily and don't look good.

Creating images in 16x9 aspect ratio would help.


fix: res/automation/automation-accounts/Sofwareupdateconfigurations isenabled parameter

Description
Api version update for softwareUpdate feature
Fixes #2402
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[x] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[X] I'm sure there are no other open Pull Requests for the same update/change
[X] I have run Set-AVMModule locally to generate the supporting module files.
[X] My corresponding pipelines / checks run clean and green without any errors or warnings

Issue #2402 is no more present also in version 2019-06-01 of Microsoft.Automation/automationAccounts/softwareUpdateConfigurations API. So closing this request


Add spanish translation for surveys

Thanks a lot @cokeperez !
There's something that could be misinterpreted. When prompting the question "Te importaria contestar a alguna pregunta?" one of the choices is "Claro". In English "Sure" could be valid but in Spanish "Claro" means exactly the opposite for this example. I would change the question and/or "Claro". What do you think? As a spanish speaker I know this is tricky :)

@patedit I would change the question it's quite tricky. @cokeperez what do you think about
'¿Quieres contestar alguna pregunta?' or something similar so the answer fits better?

@patedit @papajulio thank you for your feedback.
The original question in english is 'Mind taking a quick survey?' so maybe we can put '¿Podrías contestar una breve encuesta?'
What do you think?

I like it! As soon as you change it, I'll merge your PR. Thanks @cokeperez @papajulio

Done :)
Thx @patedit!

Thanks guys!


css modules aren't being built? or css is being excluded?

when I build normally I get css chunks, but when I deploy using this plugin, none of my css files get deployed and they don't appear on the .next directory locally.
Because of this not all of my styles get deployed

Looks like it may be because I had my dev server running in a different directory, checking now...

Yup this one was my fault


bug: [Bug] ngModel not working in ion-toggle, ion-searchbar

Type: bug
Ionic Version: 2.x
Platform: all
The ion-searchbar and ion-toggle outputs errors with [(ngModel)] since last update to ionic-angular beta.10 with the next code:
<ion-searchbar debounce='200' [(ngModel)]="searchQuery" placeholder='Buscar'></ion-searchbar>
<ion-toggle [(ngModel)]="toggleValue"></ion-toggle>

export class CustomersPage {
  public searchQuery: string = ''
  public toggleValue: boolean = true
  ...
}

Error output:

Hello, thanks for opening an issue with us! Would you be able to provide a plunker that demonstrates this issue? Thanks for using Ionic!

Basic start plunkr?

@Luchillo sure, here is the link to the one that is included in the issue template http://plnkr.co/edit/me3Uk0GKWVRhZWU0usad?p=preview. Thanks!

How am i supposed to import the @angular/forms package?, i'm editing the config.js systemjs file but i see it locks the angular version to RC.1, i increased to RC.4 but i'm stuck in adding the SystemJS mappings, this is what i have so far:
(function(global) {

  var ngVer =<EMAIL_ADDRESS>// lock in the angular package version; do not let it float to current!

  //map tells the System loader where to look for things
  var  map = {
    'app':                        'src', // 'dist',
    'rxjs'<EMAIL_ADDRESS>    '@angular/forms':             'https://npmcdn.com/<EMAIL_ADDRESS>    'angular2-in-memory-web-api': 'https://npmcdn.com/angular2-in-memory-web-api' // get latest
  };

  //packages tells the System loader how to load when no filename and/or no extension
  var packages = {
    'app':                        { main: 'app.ts',  defaultExtension: 'ts' },
    'rxjs':                       { defaultExtension: 'js' },
    '@angular/forms':             {},
    'angular2-in-memory-web-api': { defaultExtension: 'js' },
  };

  var packageNames = [
      '@angular/common',
      '@angular/compiler',
      '@angular/core',
      '@angular/http',
      '@angular/router',
      '@angular/platform-browser',
      '@angular/platform-browser-dynamic',
      '@angular/router-deprecated',
      '@angular/testing',
      '@angular/upgrade',
  ];

  // add map entries for angular packages in the form '@angular/common': 'https://npmcdn.com/<EMAIL_ADDRESS>  packageNames.forEach(function(pkgName) {
    map[pkgName] = 'https://npmcdn.com/' + pkgName + ngVer;
  });

  // add package entries for angular packages in the form '@angular/common': { main: 'index.js', defaultExtension: 'js' }
  packageNames.forEach(function(pkgName) {
    packages[pkgName] = { main: 'index.js', defaultExtension: 'js' };
  });

Sorry about the last comment, here's the plunkr you needed, i think it happens when i try to use the new Forms API and deprecate the old form API: http://plnkr.co/edit/N7teQ0?p=preview

Ahh, so the issue is that we do not support the new refactored forms module yet, although this has already been fixed for the upcoming beta.11 release. Thanks for using Ionic! For now i would recommend using the deprecated forms api.

I didn't though it was that until now that i replicated the issue and it worked until i made the deprecation provider thing.


Number of placeholder and arguments mismatch in log message

Describe the bug
We have some log like:
log.debug("[{}] Redirecting the rest call to {}: cluster={}", redirect, peerClusterData);

The number of {} is different to arguments count.  And for exception logging:
log.warn("Failed to offload: {}", e.getCause());

The last argument type is Throwable , here is last argument will not be treated as a format argument even there is a placeholder.

This was fixed by #4436


⚠ Bofrost.es has degraded performance

In f5e6c98, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1763 ms

Resolved: Bofrost.es performance has improved in 7f12e78 after 9 minutes.


Introduce separate Akka dispatchers for CouchDB and Kafka Clients (#2954)

Rest of system continues to use the default system dispatcher

Refs #2954

Description
This reopens the previous  #2956 PR; fork-join-executor wasn't the right choice previously and it is using Thread Pool dispatchers now, which are the correct way to handle this kind of IO separation with Akka. Defaults are set to what should be a reasonable starting point, especially given that couch and kafka now have their own separate execution pools from the "Default"/main system.

Kafka and CouchDB clients each get their own dispatchers

This should prevent all of the akka based stuff from competing constantly for threads
Kafka and Couch can be tuned now based on individual needs
Using thread-pool dispatchers, which are best suited for these processes (default is fork-join)

Dispatchers are defined in common reference.conf, so config can be overridden by dependents

Currently, OpenWhisk is sharing a single fork-join-executor across the board for the entire ActorSystem, which is less than ideal especially when dealing with potentially blocking IO.
Related issue and scope

[x] I opened an issue to propose and discuss this change (#2954 )

My changes affect the following components

[ ] API
[ ] Controller
[x] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[x] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[x] Bug fix (generally a non-breaking change which closes an issue). (sort of a bug fix)
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes. (not easily testable in unit/integration)
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #3515 into master will increase coverage by <.01%.
The diff coverage is 75%.

@@            Coverage Diff            @@
##           master   #3515      +/-   ##
=========================================
+ Coverage      75%     75%   +<.01%
=========================================
  Files         128     128
  Lines        6081    6082       +1
  Branches      398     389       -9
=========================================
+ Hits         4561    4562       +1
  Misses       1520    1520

Impacted Files
Coverage Δ

.../whisk/core/database/RemoteCacheInvalidation.scala
0% <0%> (ø)
:arrow_up:

.../scala/whisk/core/database/CouchDbRestClient.scala
87.23% <100%> (+0.27%)
:arrow_up:

...n/scala/whisk/core/database/CouchDbRestStore.scala
74.03% <100%> (ø)
:arrow_up:

...n/scala/whisk/core/connector/MessageConsumer.scala
83.56% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7bd6474...74c4ac8. Read the comment docs.

@bwmcadams @chetanmeh this might be of use for other datastores so I wonder if we should rename the couch configuration to data store.

this might be of use for other datastores so I wonder if we should rename the couch configuration to data store.

+1

Makes sense to me. I know it occurred to me while I was putting this
together, and tunable dispatchers for each component like this is a good
thing.
On Tue, Jun 12, 2018, 05:18 Chetan Mehrotra<EMAIL_ADDRESS>wrote:

this might be of use for other datastores so I wonder if we should rename
the couch configuration to data store.
+1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-openwhisk/pull/3515#issuecomment-396540431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGANvOozHZ-ZC8VVTHhxCt-h87zkx_hks5t75V3gaJpZM4TD11T
.

@bwmcadams  #3779 introduces a new S3AttachmentStore where I was thinking to use the dedicated dispatcher. Do you plan to rename the dispatcher from couch-dispatcher to db-dispatcher?

@chetanmeh good question. I think the quandary is whether there's a single shared db-dispatcher or a specific one per database implementation. My preference/instinct would be to have one per database implementation. The way a particular database driver is implemented can vary vastly from one to the other in terms of what the best dispatcher tuning is for it. Sharing a single dispatcher may not be ideal.

@bwmcadams There are 2 aspects

Have a dedicated separate dispatcher for db operations
Dispatcher being tuned per DB driver implementation

Currently we have few storage impls which use Akka HTTP stack like CouchDB, S3 and ElasticSearch. So for them I think it would be better to have a generic db-dispatcher which is used by default. If any setup needs specific tuning then config can still be overridden for that deployment and later we can see if it makes sense to use a dedicated dispatcher for that kind of db.
So to start with lets have a generic db-dispatcher and later based on learning we can define specific one. This would allow us to at least meet 1 and still enabling option for 2.
Thoughts?


Prevent current_user_permissions from returning None

Purpose

Fix current_user_permissions in the API for nodes where you are a read contributor.

Bug Description

Visit /v2/users/me/nodes/ and find a project for which you are a read contributor. Note that the "current_user_permissions" attribute is null.

Visit osf.io/prereg/, click "Preregister a project you have on the OSF" and note that the typeahead field doesn't list your project. Note the error in the console and the error sent to sentry in the networking tab.

Ticket
https://openscience.atlassian.net/browse/PLAT-1189

Build failure is unrelated to this PR and has been fixed. This is good to merge.


Archive AppVars after running programs

This is a feature I've been thinking about for a while, what if Cesium had an option to archive all unarchived Appvars (if there's space) after running an assembly program?  This would prevent almost all high score save losses (Like my Calcuzap score that just keeps getting wiped).

No; the programs should do this. Contact the developer.


runtimeType from object returned by async function prints as _Future

Testing this on DartPad, which is really dart2js.
Consider this code:
import 'dart:async';

Future<int> doAsyncThing() => new Future.value(42);

usingAsync() async => doAsyncThing();

main() {
  var thing = usingAsync();

  // what is the runtimeType of thing ?
  print(thing.runtimeType); // _Future

}

Actual: This code will print _Future
Expected: Future

I believe this is actually working as intended: the runtimeType is the type of the implementation of the future. Turns out that Future is an interface, and it's factory methods allocate a private class called _Future.
Not always we use the same library code for the VM and for dart2js, but in this case we do. So if you run your example in the VM, it will also print _Future.

Ah, interesting. Good to know that runtimeType can return privately named implementation types. Thanks for the quick response!


Switch build to CMake

Using CMake will make it easier to build the library on variety of systems. You can find a working CMakeLists.txt file in this PR for Conan Center Index: https://github.com/conan-io/conan-center-index/pull/3283

For those interested, I've got a fork up and running here which is CMake based, cross platform (compiles on MSVC as well) and incorporates some of the stale PRs in this repo.


External service routing method can’t transver bot to human agent

Hello i have some problem when integrating Rocket.chat with hubot-natural bot, i want to set my bot agent as default agent for every guest visiting live chat, so i set Livechat Routing Method as External Service, i made my own External Queue Service URL and set mybot details as the return from my endpoint as mention in documentation, and everything is going well.
the problem is when i using External Service routing method, i can’t transver bot agent to human agent when customer want to talk to human (it’s always return false, “there is no one online right now”), but if i using other routing method everything is going well, bot can transfer chat to other human agent as i wish.
thank you for your help …

Hi @alfabaria.
What method are you using to transfer the chat to another agent?

Hello Please provide some sample tutorial Livechat Routing Method as External Service

Please, take a look at our REST API docs:
https://rocket.chat/docs/developer-guides/rest-api/livechat/
There are specific method to forward or transfer a Livechat room.


fix replicate.stream example

The docs for replicate.stream() don't have any input:
for await (const event of replicate.stream("meta/llama-2-70b-chat")) {
    process.stdout.write(`${event}`);
}

See https://github.com/replicate/replicate-javascript/tree/6dd5b21884e5dab8d137818e3c43ab14f4335f30#replicatestream
Let's update this to a working example.

Like this:
const input = {
  prompt: "Can you write a poem about open source machine learning?",
}

for await (const event of replicate.stream("meta/llama-2-70b-chat", { input })) {
  process.stdout.write(event.toString());
};


error while installing tellurium using pip

Collecting python-libnuml>=1.0.0 (from tellurium==2.2.10)
Using cached python-libnuml-1.1.6.tar.gz (5.7 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [9 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/tmp/pip-install-b9rmal_o/python-libnuml_705c84aba0314e3bb2bd8f4c49e4a3cd/setup.py", line 112, in
raise ValueError("Invalid libNuML Source directory, no VERSION.txt file")
ValueError: Invalid libNuML Source directory, no VERSION.txt file
Using libNuML from: /tmp/pip-install-b9rmal_o/python-libnuml_705c84aba0314e3bb2bd8f4c49e4a3cd
Using VERSION.txt: /tmp/pip-install-b9rmal_o/python-libnuml_705c84aba0314e3bb2bd8f4c49e4a3cd/VERSION.txt
['PKG-INFO', 'setup.py', 'python_libnuml.egg-info', 'setup.cfg', 'README.md']
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Seems like this has nothing to do with tellurium, pip tried to install libnuml, and it failed to compile on your machine. Could you let us know which:

python version
architecture  / os

you are running, then we can make a new release of the dependency to get you going.

@jurquiza Did this answer your question?


Automate exporting BOM from Inventor 2022

There are 67 parts in Ventilator. We can get XLSX files of Bill of Material (BOM) from Inventor. Attached is a CSV file of a BOM with all parts . There is an API for BOM generation and export.
What is required
There should be a way to automate generating BOMs for all subassemblies. So that data generated can be used to generate web pages or request forms.
Subtasks:

[ ] Check if we can use API
[ ] Determine how to use CSV files.

How do you know it has to be done
Wiki and parts list have to be generated by hand. Automating it will help and reduce workload.
Link to requirements or risk analysis if applicable.
Starting points
There is an API of Inventor below are two help pages.
BOM functions with iLogic: https://help.autodesk.com/view/INVNTOR/2022/ENU/?guid=GUID-5BEAA369-CFC0-482B-B01E-76914AAA750C
BOM API functions: https://help.autodesk.com/view/INVNTOR/2022/ENU/?guid=GUID-445993C4-420A-4F54-9E8A-26AE86546706
BOM Apps in Autodesk app store: https://apps.autodesk.com/INVNTOR/en/List/Search?isAppSearch=True&searchboxstore=INVNTOR&facet=&collection=&sort=&query=bom
Don't forget

[x] Put the issue in a milestone
[x] Assign it to one of the projects
[x] Add appropriate labels
[x] Mention dependent/blocked issues if any

There is another issue 1011 so closing this one.


Dark theme not working

Hi Chris, the new Configurator UI is really nice, awesome work!
Unfortunately dark theme (#68) does not work in v. <IP_ADDRESS>. I have Windows set to all dark (both apps and system).
Thanks

Thx! It only works if you restart the configurator. It will not change while it's running.

I tried it, even restarted the pc, but it doesn't work. Tried on Windows 10 1909 stable and 2004 preview.

@Martin5001 Weird, it's working fine here on 2004

I was on <IP_ADDRESS> (free version from GitHub) and couldn't make the app go dark either. I tried to re-install (while using dark system theme), restart the configurator, restart the PC, but it stays light. I tried switching system theme to light and back to dark and then do the above steps, but I just couldn't get it to work.
I'm using Surface Laptop 3 with 1909 (build 18363.815).
Windows Store version <IP_ADDRESS> has working dark mode though, I tried it just now.

@ArttuLai I noticed the same with the store version. So i will open a issue today. https://github.com/Kinnara/ModernWpf

Should be fixed now in <IP_ADDRESS> after update https://github.com/Kinnara/ModernWpf/releases/tag/v0.9.2


Component tags are always highlighted in red (idem like #1172)

Same problem like #1172.
Same thing in the volare-starter project (pulled, not changed in any way)

jsx property set as requested in tsconfig.json
"jsx": "preserve"

How can I debug this problem further ?

I have the same problem for "jsx": "preserve" too.

This error is due to missing @vue/runtime-dom because you do not have install node_modules in volare-starter.

@plashenkov Make sure you have put it in compilerOptions, see https://github.com/johnsoncodehk/volar/issues/1219#issuecomment-1104548432.

Sorry, no change.  Example in starter project, after vscode reload

package.json
{
  "name": "volar-starter",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "vue-tsc --noEmit && vite build",
    "serve": "vite preview"
  },
  "dependencies": {
    "vue": "next"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "latest",
    "@volar-plugins/prettier-html": "latest",
    "@vue/compiler-sfc": "latest",
    "@vue/runtime-dom": "^3.2.31",
    "typescript": "latest",
    "vite": "latest",
    "vue-tsc": "latest"
  }
}

tsconfig.json
{
  "compilerOptions": {
    "target": "esnext",
    "module": "esnext",
    "moduleResolution": "node",
    "strict": true,
    "jsx": "preserve",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "lib": ["esnext", "dom"],
    "types": ["vite/client"]
  },
  "include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx", "src/**/*.vue"]
}

@stefaanMLB Please check if you have disabled editor.semanticHighlighting.enabled in vscode settings, you need to enable it.

This was set to configuredByTheme, I changed to true`.  This doesn't help.

I have the same problem.

@stefaanMLB Please follow steps.

config "volar.vueserver.useSecondServer": true and "volar-language-features-2.trace.server": "verbose" in volar-starter vscode workspace settings.
Reload vscode window
Open src/App.vue
Open output -> Volar - Second Language Features Server, search Received response 'textDocument/semanticTokens/range and show me the response log.

@johnsoncodehk
I tried the above Step, but unlike yours, the contents of the "data" is empty.

@johnsoncodehk thanks for the precise instructions. appreciating it.
I have the search string 5x in the output, so I included some more text just in case.  Seems the text you're looking for is in there twice
[Trace - 07:11:35] Received response 'textDocument/semanticTokens/range - (5)' in 3141ms.
Result: {
    "resultId": "1651727495813",
    "data": [
        2,
        3,
        10,
        12,
        0
    ]
}

[Trace - 07:11:35] Received response 'textDocument/documentLink - (7)' in 2502ms.
Result: [
    {
        "range": {
            "start": {
                "line": 1,
                "character": 27
            },
            "end": {
                "line": 1,
                "character": 44
            }
        },
        "target": "file:///c%3A/Users/lcartreul/Documents/projecten/volar-starter/src/assets/logo.png"
    }
]

[Trace - 07:11:35] Received response 'textDocument/codeLens - (8)' in 2455ms.
Result: []

[Trace - 07:11:35] Received response 'textDocument/codeLens - (6)' in 2659ms.
Result: []

[Trace - 07:11:35] Received request 'vue/docVersion - (10)'.
Params: {
    "uri": "file:///c%3A/Users/lcartreul/Documents/projecten/volar-starter/src/App.vue"
}

@negipoyoc Do you have install node_modules of volar-starter?
@stefaanMLB Seems you have correct response data, please try:

Update vscode if it can.
Check what extensions it may affect vue document you have installed and try disable it just keep volar. (Help: Start Extension Bisect command may help)

@johnsoncodehk
didn't help.
I tried to uninstall and reinstall Volar, but it now fails after every reload (no code coloring + below error message)

@johnsoncodehk Hello. Thank you for your answer.
It seems that the data was Empty because I checked the output without resolving the dependency with volar-starter.
After doing the npm install, the Component was highlighted successfully.
I then reviewed the tsconfig.json of my project, which has a similar problem, while looking at the tsconfig.json of volar-starter.
By adding the following to tsconfig.json, I was able to get the highlighting and the problem was resolved in my project.
 "compilerOptions": {
    "jsx": "preserve",
  }

Thank you for addressing the problem despite my simple carelessness.

Same here.

@stefaanMLB For that message, see https://github.com/johnsoncodehk/volar/issues/1124#issuecomment-1123312339.
But I have no clue as to why your component is showing red, the LSP is returning the expected response, the VSCode settings is find, if it is not the influence of other extensions, it can only be considered a problem with VSCode (but this is the least likely).
@negipoyoc It's ok, I will improve user guidance.
@yoyo837 See #1192.

@johnsoncodehk I tried disabling any exntensions that could interfere (like vetur), but no luck.
I can live with the problem, I'll try volar out on my home computer which has less extensions installed. Wo't have time in the first few days though.

@johnsoncodehk, created a new project in Nuxt 3 on a virtual machine Windows 10 (VMware). In the editor VSCode installed only one extension - Vue Language Features (Volar).
With Developer: Inspect Editor Tokens And Scopes you can see additional data, how the tag marked in red is interpreted.

The custom components look the same. In this case, the application is correctly displayed and works in the browser.
With this information in mind, how can I try to solve this problem?

Please update to v0.34.17.

Please update to v0.34.17.

Updated to version v0.35.0 and now everything is correct.
Thank you! 👍

Same here, update to v0.35.0 has solved the problem.

We using explicit components import and now it is hard to see what wasn't imported correctly

We using explicit components import and now it is hard to see what wasn't imported correctly

The past behavior was abandoned to resolve the situation in this issue, if you need the past behavior, please open a new feature request.


User Ad Groups - returns "Cannot index into a null array"

I receive an error "cannot index into null array" for some machines. These machines have an $account.LastLoggedOnUserSID of S-1-5-21-####-####-####-500
I get the error Cannot index into a null array. on line 13, which is $groups = $ds.FindOne().Properties['memberof']
I think that we need to only access the 'MemberOf' property only if $ds.findone() has results.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/security-identifiers-in-windows

Fixed with latest merge


Running in windows11 !!!

My computer (nvida 4090 cuda11.6，cudnn<IP_ADDRESS>)
Some missing dependencies :
conda install pytorch==1.13.0 torchvision==0.14.0 torchaudio==0.13.0 pytorch-cuda=11.6 -c pytorch -c nvidia
pip install filelock
pip install spacy
pip install segment_anything
pip install openai==0.28.1
pip install ipdb
pip install pillow==9.5.0
pip install timm==0.6.7
pip install git+https://github.com/facebookresearch/segment-anything.git

modify run.py line:78
seed = np.random.randint(0, high=2 ** 32 - 2, dtype=np.int64)
modify util/utils.py line:248
with open(yaml_path, 'r',encoding="UTF-8") as file:
modify run.py line:69
with open(Path(model.run_dir) / "config.yaml", "w",encoding="UTF-8") as f:
modify run.py line:199
with open(save_root / 'regenerate_info.json', 'w',encoding='UTF-8') as json_file:
modify models/models.py line:575
self.run_dir = run_dir_root / f"Interp-{dt_string}_{inpainting_prompt.replace(' ', '_').replace(':', '_')[:40]}"
modify models/models.py line:418
self.run_dir = run_dir_root / f"Gen-{dt_string}_{inpainting_prompt.replace(' ', '_').replace(':','_')[:40]}"

Thanks for sharing that! Please let me know how you installed the nvidiacub and pytorch3d on Windows if you still remember that. I really appreciate any help you can provide.


Optimize the realization of SchemaChange

The code in schema_change.h in not good. There are many unused argments, for example tablet in the constructor. And some variable names are not explicit.

Fixed by #1108


Autocommit for script

Since I'm used to pgAdminIII I'm looking for a DBeaver configuration which ensure the same transaction behaviour when running scripts.
Main demands:
1 run whole script if nothing selected
2 run selected part of script if anything selected
3 autocommit if there is no explicit BEGIN transaction called
4. autorollback in case of error
I almost succeeded except of:

no auto-rollback if explicit BEGIN was issued and error is raised during execution (regardless running sql command or script)
when running script, it commits every single line, regardless of settings "Scripts/Commits type" set to "At script end".

So far I found following settings which might help to reach requested behaviour but, as said, with no full success:
Settings:

Autocommit set in toolbar
In preferences Editors/SQL Editors/SQL Processing/Scripts:
-- Commit type: At script end
-- Error handling: Stop+rollback
In preferences Error handle/Execute errors
-- Rollback on Error: true

Sorry for the long answer. Is it possible to give a Script example?

there is no update on issue. if it is still actual for you - feel free to reopen the issue


Add Custom League Sessions

Implement support for the /data/league/cust_league_sessions endpoint.

I'll try to do something useful with this

Cheers! I'm just not a member of any actual custom leagues so don't have any example data.

Thanks heaps for adding this, @dennis! Sorry the merge was a bit rocky.


Preserve kind of variable declaration in invalid-requires

I noticed that this was always using var even if const was used
before the transform.

We didn't use let or const at FB when I created this codemod :smiley: thanks for fixing this!

That's what I figured. No problem!


gpu support

From your introduction, it says "support inference with accelerated GPU". How to make it happen? Thanks!

Sorry for the late reply.
It does support GPU inference because we use TensorFlow Python APIs which supports GPU. You can install tensorflow-gpu and configure CUDA dependencies before running simple_tensorflow_serving.

can it support GPU other than nvidia?


Fix explain bug with RuleSelector, improve explain output

While trying out https://github.com/PlasmaFAIR/fortitude/pull/108/commits/7a4b965983001ab387c96d121a0c4c231723afb1 in https://github.com/PlasmaFAIR/fortitude/pull/108, I found that the explain command was no longer working properly. This PR fixes the bug, and while I was at it I also improved the output for explain, updated the README, and improved the help text that's printed when things go wrong.
explain now prints the name of the rule alongside the code, but it's in camel-case. There are a few Rust libraries that allow you to convert to other cases, like sentence case, but these aren't clever enough to rename IOError to IO error or NonStandardFileExtension to Non-standard file extension, so for now I've left it at camel-case.

I added a small function to the map_codes macro so you can get the name of a Rule from the enum, but this feels like something that should have already been there. Have I overlooked where this is defined?


Correctly support 8 digit TOTP

This is necessary to allow supporting 8 digit TOTPs (hello, Blizzard Authenticator)

Thank you @lukegb for your contribution


Add cover images to all snippets

For SEO and overall aesthetic purposes, we could expand the cover image mechanism to all snippets. This will require roughly the following:

Move all assets to their own repository where we can reuse them easily and get their metadata as necessary.
Replace existing assets with lower quality ones (not the actual output images).
Create a proper mechanism for image credits that will inject the data into the snippet.
Update blogs to use the new mechanisms.
Update designs with the new covers.
Update all snippets to use covers.

After further investigation, this project is going to be scrapped. Any mocks we've tried with images, patterns, colors etc. result in distractions for the users and less accessible content. We'll keep using images in blog content only for the time being.


Can't remove a codebase

Screencast from 04-06-2017 12:53:03 PM.webm.zip

FYI, the APIs don't support deleting a codebase, so the feature is disabled in the codebases page. I would also like the ability to delete a space.

@qodfathr @pmuir @aslakknutsen will we be allowed to remove a codebase?

Can we edit them as an alternate to correct bad URL's for example?
On Fri, Apr 7, 2017 at 5:14 PM, Joshua Wilson<EMAIL_ADDRESS>wrote:

@qodfathr https://github.com/qodfathr @pmuir https://github.com/pmuir
@aslakknutsen https://github.com/aslakknutsen will we be allowed to
remove a codebase?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ui/issues/552#issuecomment-292653550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANHdNiNxP_QiAcT7Zw3pwJYfxKh4woDhks5rtqdIgaJpZM4M14Sw
.

Yes, you should be able to remove a codebase. Of concern is that if having at least one codebase listed is the only way to manipulate workspaces, that would be a problem (hence why workspaces probably need their own management screen).
It is not unreasonable to have a Space with no codebases -- e.g., that's essentially what Trello is.

Why do you need a workspace without a code base?  I don't see that as a
limitation.
On Sat, Apr 8, 2017 at 11:44 AM, Todd Mancini<EMAIL_ADDRESS>wrote:

Yes, you should be able to remove a codebase. Of concern is that if having
at least one codebase listed is the only way to manipulate workspaces, that
would be a problem (hence why workspaces probably need their own management
screen).
It is not unreasonable to have a Space with no codebases -- e.g., that's
essentially what Trello is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ui/issues/552#issuecomment-292726046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANHdNlGH8kr5FgvzaS95mhWmCrjB6K5Vks5rt6tHgaJpZM4M14Sw
.

@cctrieloff I was thinking this:

Have a codebase  (via new Space, import, etc.)
Create a workspace
Remove the codebase
??? How do I deal with the workspace created in step 2? How do I see it? Deprovision it? etc.

We should delete the workspace when you remove the codebase. The system
should clean that up automatically.
Carl.
On Mon, Apr 10, 2017 at 4:20 PM, Todd Mancini<EMAIL_ADDRESS>wrote:

@cctrieloff https://github.com/cctrieloff I was thinking this:

Have a codebase (via new Space, import, etc.)
Create a workspace
Remove the codebase
??? How do I deal with the workspace created in step 2? How do I
see it? Deprovision it? etc.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ui/issues/552#issuecomment-293066837,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANHdNtNVCw588kaKtfycmSJzARWZyIHuks5ruo7ygaJpZM4M14Sw
.

@aslakknutsen is this something that you could do on the backend?

@cctrieloff but codebases are not associated 1:1 with workspaces. i.e., I may have 5 codebases and only one workspace which I end up bouncing between them (e.g. need to do that on Free). There are so many potential use cases, that I'd be very concerned about not having some sort of workspace management screen. Maybe not a priority for this month, but probably something that needs to get addressed in May.

@qodfathr I might be mistaken but I thought you could only run one workspace at a time but each was directly associated with a codebase. As far as i remember, Che doesn't really work in a way for you to use different codebases with the same workspace.

A workspace is a docker image that is built based on the stack the codebase needs. So if you have a Java codebase, then the workspace needs to have Java installed. Whereas, if it is a Node project then you don't want Java installed but it will have Node.

right now they 1:1 and our UX etc oly assumes a 1:1 mapping. Let's auto
clean up the resources for now. One day if we decide to change the
relationship we can look at more options then.  I would prefer to be more
aggressive in clean up as we pay for any orphaned resources.
Carl.
On Mon, Apr 10, 2017 at 9:48 PM, Joshua Wilson<EMAIL_ADDRESS>wrote:

@qodfathr https://github.com/qodfathr I might be mistaken but I thought
you could only run one workspace at a time but each was directly associated
with a codebase. As far as i remember, Che doesn't really work in a way for
you to use different codebases with the same workspace.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ui/issues/552#issuecomment-293126380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANHdNsiiWDjAIz7Z5SFdGwOlSHzaroJZks5rutvsgaJpZM4M14Sw
.

@dlabrecq please follow up on this. We need to be able to clean up the codebases.

The codebases UI has a disabled option to delete a codebase; however, the Restful API does not support it. When the API has been implemented, we can enable the feature in the UI.

We decided this morning that we will remove this option from the kabob in the UI until the API has been created to reduce confusion for users.

Created PR https://github.com/fabric8-ui/fabric8-ui/pull/1869 to omit the disabled option.


Please provide better instructions on how to implement the script to detect a change in the bus id

you don't provide any details on how to create the file with the bash script.  its unclear how to do the final steps.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0e03790a-1bf9-146d-704b-6816d475064b
Version Independent ID: ad5f6be7-e089-161f-306c-39d10e7ab0a0
Content: Azure N-series driver setup for Linux
Content Source: articles/virtual-machines/linux/n-series-driver-setup.md
Service: virtual-machines-linux
GitHub Login: @dlepow
Microsoft Alias: danlep

@queglay Thanks for the feedback! We are currently investigating and will update you shortly.

@queglay I have assigned the issue to the content author to investigate further and update the document as appropriate.
@dlepow can you please take a look? Appears to be referencing this section: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#x11-server


Search with datetime=37-01-01T12:00:27.87Z returns a 500 instead of a 400

From Planetary Computer:

GET Search with datetime=37-01-01T12:00:27.87Z returned status code 500 instead of 400

Closing as fixed:
$ curl -i https://planetarycomputer.microsoft.com/api/stac/v1/search\?datetime\=37-01-01T12:00:27.87Z
HTTP/2 400
content-length: 146
content-type: text/plain; charset=utf-8
strict-transport-security: max-age=15724800; includeSubDomains
access-control-allow-origin: *
access-control-allow-credentials: true
x-cache: CONFIG_NOCACHE
x-azure-ref: 0wNzaYwAAAADJ9W8EP7lRQZbxDnrsEW4CV1NURURHRTA4MTAAOTI3YWJmYTYtMTlmNi00YWYxLWEwOWQtYzk1OWQ5YTFlNjQ0
date: Wed, 01 Feb 2023 21:42:24 GMT

Invalid parameters provided 1 validation error for SearchPostRequest
datetime
  invalid literal for int() with base 10: b'37-0' (type=value_error)


Update README.md

In readme.md:
npm install https://github.com/LLK/scratch-audioengine.git

Now it should be:
npm install https://github.com/LLK/scratch-audio.git

make a PR?

thanks, all set