Feature Request: Would it be possible to create an entity that has the "effect_list" for the various devices.

Govee Device SKU
H70B1
Govee2MQTT Version
2024.01.24-ea3cd430
Describe the issue
Would it be possible to create an entity that has the "effect_list" for the various devices.
`homeassistant/light/gv2mqtt-698FC58884592A52/config
{
"availability_topic": "gv2mqtt/availability",
"name": null,
"origin": {
"name": "gv2mqtt",
"sw_version": "2024.01.24-ea3cd430",
"url": "https://github.com/wez/govee2mqtt"
},
"device": {
"name": "Smart Curtain Lights",
"manufacturer": "Govee",
"model": "H70B1",
"via_device": "gv2mqtt",
"identifiers": [
"gv2mqtt-698FC58884592A52"
]
},
"unique_id": "gv2mqtt-698FC58884592A52",
"schema": "json",
"command_topic": "gv2mqtt/light/698FC58884592A52/command",
"state_topic": "gv2mqtt/light/698FC58884592A52/state",
"optimistic": false,
"supported_color_modes": [
"rgb",
"color_temp"
],
"color_mode": true,
"brightness": true,
"brightness_scale": 100,
"icon": "mdi:light-bulb",
"effect": true,
"effect_list": [
"",
"A Fishing Cat",
"Aircraft Battle",
"Alternate",
"Artist Palette",
"Astronaut",
"Atlantis",
"ATREIDES-FREMEN",
"Autumn Leaves",
"Ballet Girl",
"Bat",
"Big Ben",
"Big Bus",
"Big Panda",
"Big Pendulum",
"Birds Flying",
"Birthday Cake",
"Bonsai",
"Bouncing Ball",
"Bubble",
"Burj Khalifa",
"Butterfly",
"Cable Car",
"Cactus",
"Camping",
"Candy Cane",
"Candy Crush",
"Cannibal Flower",
"Carousel",
"Cherry blossoms",
"Christmas Bell",
"Christmas Gift",
"Christmas Gift Box",
"Christmas Stocking",
"Christmas Tree",
"Christmas Wreath",
"Circus",
"Clown",
"Clownfish",
"Coachella Poster",
"Code",
"Countdown",
"Crab",
"Crossing",
"Cupid's Arrow",
"Demon Power",
"Dinosaur",
"Dodging",
"Dot Eater",
"Dove",
"Dr. Duck",
"Drift Bottle",
"Drinks",
"Duck Bathing",
"DUNE",
"Easter Egg",
"Egyptian Fresco",
"Eiffel Tower",
"Elk",
"Falling Petals",
"Ferris Wheel",
"Finger Heart",
"Fire",
"Fireplace",
"Flamingo Couple",
"Forest",
"Forest Fireflies",
"Fox",
"Game Controller",
"Ghost",
"Gingerbread House",
"Gingerbread Man",
"Golden Gate Bridge",
"Gopher",
"Gourmet",
"Gradient Movement",
"Graffiti",
"Greedy Snake",
"Groovy",
"HARKONNEN",
"Hatch",
"Heart Scale",
"Heartbeat",
"Horse Head",
"Hot Air Balloon",
"Ice-cream Cone",
"Jellyfish",
"Jumping Chicken",
"Lighthouse",
"Lion",
"Little Whale",
"Lollipop",
"Lottery Machine",
"Lotus Pond",
"Love",
"Love Heart",
"Magic Hat",
"Maiden",
"Maze",
"Meteor",
"Mondrian",
"Moon",
"Moonlight",
"Mount Fuji",
"Mountain Forest",
"Mountaintop",
"Mushroom",
"Music Note",
"Music: Crossing",
"Music: DreamColor",
"Music: FallingSand",
"Music: FloatingMist",
"Music: MeteorShower",
"Music: Spectrum",
"Orbital Rail",
"Owl",
"Panda",
"Parabola",
"Peach Checkers",
"Peacock",
"Piggy Bank",
"Pineapple House",
"Pizza Monster",
"Planet",
"Poker",
"Pumpkin",
"Rabbit",
"Rabbit Running",
"Racing",
"Rainbow",
"Rainbow Swirl",
"Reverse",
"Rhomb",
"Ring Toss",
"Ripple",
"Rocket",
"Saint Patrick's Day",
"Sakura",
"Santa Claus",
"Sea Horse",
"Sea Island",
"Sea Turtle",
"Seesaw",
"Shiny Rainbow",
"Shoot Hoops",
"Siren",
"Skateboard",
"Sled",
"Smudge",
"Snowman",
"Soccer",
"Soccer Juggling",
"Soothing",
"Space",
"Space Walk",
"Spider",
"Spin",
"Stack",
"Star",
"Starfish",
"Starry Night",
"Strike",
"Sunflowers",
"Sunrise",
"Sunset",
"Surfing",
"Telephone",
"The Pyramids",
"The Scream",
"The Son of Man",
"The Taj Mahal",
"Tic-Tac-Toe",
"UFO",
"Umbrella",
"Undersea King",
"Valentine's Day",
"Water Drop",
"Waterfall",
"Wave",
"Weightlifting",
"Whale",
"White Swan",
"Windmill",
"Windmill Kingdom",
"wine glass",
"Yoga",
"Zombie Hand"
],
`
Startup Diagnostics
This is not a startup issue.
Additional Logs
No response
Home Assistant Logs
No response
Anything else?
This would be similer to the entity that WLED creates.
select.wled_preset

After some more digging.  HA MQTT has the support for "effect_list" under the light discovery. https://www.home-assistant.io/integrations/light.mqtt/.   For some reason an entity is not being created for the "effect_list".

Never mind.  Figured out how to get the effect_list into an input_select
action:

service: input_select.set_options
data:
options: "{{ state_attr('light.smart_curtain_lights','effect_list') }}"
target:
entity_id:
- input_select.curtain_light_presets
service: input_select.set_options

Can I send a custom image to H70B1 ?


RPI3 tcam-capture

As soon as I select my device in menu, I get:
DEBUG:tcam_capture.TcamView:Created pipeline and set to READY
INFO:tcam_capture.TcamView:Setting state to PAUSED
Traceback (most recent call last):
File "tcam-capture", line 226, in open_device
self.play()
File "tcam-capture", line 231, in play
self.view.play(video_format)
File "/home/pi/tiscamera/tools/tcam-capture/tcam_capture/TcamView.py", line 242, in play
if self.pipeline.get_state(1000000).state == Gst.State.PLAYING:
AttributeError: 'tuple' object has no attribute 'state'

I can comment that line out but not sure if it is a solution!

This looks like gst-python overrides are not installed or the gstreamer / gst-python package is outdated. Re-open if this is still an issue on a current Raspbian.


Fix DateTimeActionSheet not using utc dates

This would result in some fields showing up as the wrong date.

Good catch @abbiecoghlan!


feathers generate service throws typeError: cannot read property 'jest' of undefined

If you have no devDependency in your package.json the check in feathers-generator for jest will fail with an undefined object.
this line -> https://github.com/feathersjs/generator-feathers/blob/master/lib/generator.js#L40
temp fix:
npm install --save-dev jest
Error:
(node:14423) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'jest' of undefined
at ServiceGenerator.get testLibrary [as testLibrary] (/home/franzl/.nvm/versions/node/v14.18.0/lib/node_modules/@feathersjs/cli/node_modules/generator-feathers/lib/generator.js:40:59)

#https://github.com/feathersjs/cli/issues/176

#https://github.com/feathersjs/cli/issues/176

see also
https://github.com/feathersjs/cli/issues/176
https://github.com/feathersjs/feathers/issues/2426

devDependencies and the chosen testing library are always added by the generator. If they are not added in a generated app it is usually because the initial yarn/npm installation failed for some reason. It should work again when generating a new app.

strange, seems there is problem with the<EMAIL_ADDRESS>installation
but npm install<EMAIL_ADDRESS>in shell is working fine :thinking:
this command generates a error message (see below)
0 verbose cli   '/home/franzl/.nvm/versions/node/v14.18.0/bin/node',
0 verbose cli   '/home/franzl/.nvm/versions/node/v14.18.0/bin/npm',
0 verbose cli   'install',
0 verbose cli<EMAIL_ADDRESS>0 verbose cli   'axios',
0 verbose cli<EMAIL_ADDRESS>0 verbose cli<EMAIL_ADDRESS>0 verbose cli   '--save-dev',
0 verbose cli   '--cache-min',
0 verbose cli   '86400'
0 verbose cli ]

verbose stack nodemon: No matching version found for<EMAIL_ADDRESS>595 verbose stack     at module.exports (/home/franzl/.nvm/versions/node/v14.18.0/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:209:23)

feathers generate app output:
? Project name feathers-generator
? Description
? What folder should the source files live in? src
? Which package manager are you using (has to be installed globally)? npm
? What type of API are you making? REST, Realtime via Socket.io
? Which testing framework do you prefer? Mocha + assert
? This app uses authentication No
? Which coding style do you want to use? ESLint
   create package.json
   create config/default.json
   create public/favicon.ico
   create public/index.html
   create .editorconfig
   create src/app.hooks.js
   create src/channels.js
   create src/index.js
   create src/logger.js
   create src/middleware/index.js
   create src/services/index.js
   create .gitignore
   create README.md
   create src/app.js
   create test/app.test.js
   create .eslintrc.json
   create config/production.json
   create config/test.json
npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. socket.io-parser provides its own type definitions, so you do not need this installed.
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

added 166 packages, and audited 167 packages in 2s

8 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/franzl/.npm/_logs/2021-11-24T15_59_01_931Z-debug.log

><EMAIL_ADDRESS>lint
> eslint src/. test/. --config .eslintrc.json --fix "--fix"

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------```

You're right, I'm seeing an error as well but it's because of a mocha peer dependency. But that is basically the problem, if one of the installation steps fails all other dependencies don't get added and everything ends up in a weird state.

Should be fixed now in @feathersjs/cli v4.5.1

Thank you David.
5 years later and I am still hooked on feathers ... in a good way ;)


Lua filters don't receive pandoc's AST, and don't output anything

Starting with panzer 1.4, lua filters are supported (many thanks to @msprev !!). So I tried some lua filters that I wrote myself, and none of them got expected behaviour. In fact, it seems lua filters are receiving JSON, when should receive AST instead (according to pandoc's doc on lua filters).
For instance, I have this lua filter (very first example on lua filters in pandoc's doc). It should turn Strong elements into SmallCaps elements:
function Strong(elem)
  return pandoc.SmallCaps(elem.c)
end

Running directly with pandoc, it works. Using panzer, nothing happens. Below is my styles.yaml (excerpt), which only puts that lua filter to run:
Base:
  all:
    metadata:
      numbersections: true
      lang: "pt-BR"
    commandline:
      standalone: true
    lua-filter:
      - run: myfilter.lua

The filter is correctly found by panzer, and apparently runs, but no errors on lua-filter are shown when running panzer. Even print('some debug') doesn't output anything to console. I tried to use JSON on the lua filter, but I couldn't realize how to do that. My first try was like code below, withou any results:
function test(key, value, format, meta)
  return pandoc.Str(value)
end

toJSONFilter(test)

Am I missing something?

panzer is not passing jsons to lua filters. The example you give works perfectly for me, so there must be some other issue. Try this simple example:
---
style: None
lua-filter:
    - run: myfilter.lua
...

**hello world**

This produces the expected output in small caps.
Note that print will not work as you suggest as panzer communicates with pandoc over stdin and stdout. These communication channels are 'taken' and cannot be polluted with print messages from filters (the same applies to json filters). If you want to print error messages, you should do it over stderr channels not stdout (via io.stderr:write("This should go to stderr\n")). The documentation on panzer describes how to send json messages over stderr to pretty print messages.
This is actually consistent with pandoc's philosophy. Any filters should assume that stdin and stdout are 'taken' as pandoc is designed to operate on these channels -- consuming data from stdin and producing data to stdout. Diagnostics should go to some other output channel (stderr).

If you want to pretty print, use the following expression in the filter to send a json message over stderr to panzer:
io.stderr:write('{"level": "INFO", "message": "Debug message from filter here"}\n')

Lua filters are running normal. I've cleaned up my styles.yaml till the most essential parts.
But there's a problem: in pandoc's lua filters, there's a FORMAT variable that stores the format of writer, say, html or docx, for instance. In panzer's lua filters, that variable always turns to json. So, I tried to read the panzer_reserved field on AST, but the JSON_MESSAGE is a string, not a deserialized json. With code below, JSON_MESSAGE is sent to stderr:
function Pandoc (doc)
  local jsonMessage = doc.meta['panzer_reserved']['json_message'][1].c[2]
  io.stderr:write('{"level": "INFO", "message": "' .. jsonMessage .. '"}\n')
end

And the beginning of JSON_MESSAGE as printed in stderr:
[{"metadata": {"lang": {"t": "MetaInlines", "c": [{"t": "Str", "c": "pt-BR"}(...)

By now I can't continue with testing, but I'll test dkjson to deserialize that json and get the writer format. If there's a simpler method, please let me know.

Thank you for this feedback. I've completely changed the implementation based on it as the FORMAT variable is important. I've pushed a new release now. Changes to note:

FORMAT variable is now correctly set to the writer
lua filters are now applied after any json filters
print in lua now works as expected. No need to use io.stderr:write in lua filters to print messages. Note that as with pandoc, using print inside a lua filter will pollute stdout which probably won't be desirable if you are sending your document output there too
implementation is slightly faster
I fixed some bugs and improved the format of info messages

Currently, the json message panzer_reserved is stored in the AST as a string. So you are right it does need to be deserialised if you access it in a filter. The reason is that the same message is also passed as a string across stdin to scripts (preflight, postflight, etc.) so they have access to the info too. It easy to deserialise it, and I thought it simpler to keep behaviour consistent here.

It's totally working: my lua filters are running really fast, and without any modifications from using directly with pandoc. Many many thanks, @msprev !!!

Now I'm refining my workflow, and planning to create a repository with it including some panzer configuration along with my filters. Thanks!

Wonderful! I’m really glad. Let me know if any issues crop up and it would be good to share workflows.


Collapse Object widgets

I am using Object types to organise sections. it would be great if they could be collapsed and expanded, ideally defaults set in the config.yml

We have collapsible lists and list items in the UI overhaul, collapsing objects wouldn't be a stretch. I don't think we'd put it in the config just yet, but I have considered it for collapsible items in general.
I think after 1.0 we could put this in.
cc/ @neutyp

Dumb question: what is an object as opposed to a widget?
What is the benefit of seeing these collapsed, and what would they show when collapsed?

@neutyp An object is one of our widget types, that is simply used to group other widgets together.

Aha! Thanks! This should and could easily collapse in the same way that lists do :) Design should be the exact same, without the button at right to add another item

@neutyp In most cases, the user should not be able to add an item. @erquhart @Benaiah Is there any reason that we would want an object widget to be user-editable?

FYI, I wasnt implying the ability to re-arrange or delete (which are possible in list widget). I just meant the collapse function can look the exact same

Oh, of course, I misread your statement. The term object is what we call a group in JavaScript code, so I guess it just got carried over to the widget name :).

@drlogout provided a PR for this a while ago, getting it merged now. It does reuse the styling of the list expand/collapse functionality as expected.
@neutyp I do intend at some point to rename "object" to "group", agreed.

@erquhart @neutyp What about renaming it to group, but leaving object as a depreciated option?

Hi there, any action on this? Would love to see collapsed objects.
My reason is that I'm defining every JSON field for a translation file and the nesting is quite heavy.
Collapsed objects/groups would make the navigation a lot more user-friendly.

Just needs design and elbow grease :)


”Mădărășeni”, ”Tăblășeni”, ”Valea Iclandului” are listed in the drop-down menu

Description:
When user writes ”Mădărășeni”, ”Tăblășeni”, ”Valea Iclandului” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Mădărășeni"

Expected results
The location appears in the drop-down menu as "Sat Mădărășeni, MUREȘ (Iclănzel)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Tăblășeni"

Expected results
The location appears in the drop-down menu as "Sat Tăblășeni, MUREȘ (Iclănzel)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Valea Iclandului"

Expected results
The location appears in the drop-down menu as "Sat Valea Iclandului, MUREȘ (Iclănzel)".


How to change the default service prefix?

I want to make the default /micro/registry service prefix to be another, how should I do ?

please, provide more info for use case and what kind registry used. and we can decide how to do that you need.


How to use aggregation with @azure/cosmos in nosql database

Hello,
I am currently looking for the best way to use Cosmos NoSQL with TypeScript.
I have read this and this but found no documentation on how to use aggregations with @azure/cosmos.
Is this possible? Are there docs for it? And how is the type safety for it?
Any help would be appreciated.

@Robstei Could you add more details here? Aggregation is already supported with the JS SDK, so a sample would help clarify your point.


Link to Core Values file in job postings returns 404

The link to the company values is broken for at least a few of the job postings.
I saw this on the following job postings:
Engineering Manager, Cloud Application
https://boards.greenhouse.io/dbtlabsinc/jobs/4350465005
Engineering Manager, dbt Explorer
https://boards.greenhouse.io/dbtlabsinc/jobs/4351839005
For both of those, the bullet point "Aligns with [our core values" points to https://github.com/fishtown-analytics/corp/blob/master/values.md."
That link returns a 404.
I did notice that the posting for Engineering Manager, Orchestration (https://boards.greenhouse.io/dbtlabsinc/jobs/4326424005) works fine since it points to your webpage:  https://www.getdbt.com/dbt-labs/values
I hope this channel is ok to report this - I would want someone to tell me and since the 404 was in this git repo it seemed the most obvious way.

Thanks for the heads up @barlowst! We'll get these updated 👀

Yep, just confirming -  works as expected for me too (well, the first one is gone, but I assume that is expected and the role was filled).


network: Always pass --conf-file to dnsmasq

Closes #3367
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Jenkins looks happy enough, should be good to merge.


rush! gamemode crashing on fresh installation

no default settings changed but as soon as the first note is ready to hit, the game will freeze and crash instantly.

Can reproduce, seems to be related to the latest osu! judgement changes.

@ari-outi The issue has been fixed! you can try the latest release now: https://github.com/swoolcock/rush/releases/tag/2020.711.0


Library doesn't seem to work with django's ContentFile class

Library doesn't seem to work with django's ContentFile class, as described by @pwhipp on issue #2.

Actually, the library wasn't working when out of the ModelForm standard cycle: it was failing when the files were being saved manually. Fixed in b7158175ae31cc7d71743ee59163beaf62e784f0.

Thanks for addressing this so quickly. We'll be integrating the new version shortly.


Android 8.x - setTimeOut / setInterval only works when the device plugged.

Hi,
As you can see in the title on Android 8.x I have some problems. The functions above in the background only works when the device is plugged and my timer counters works fine. When the device is not charging it doesn't work expect when I unlock the screen. Any Idea / Solution / Setting ?
Thanks.

There are two threads of JavaScript execution. WebView and WebCore. WebView is where settimeouts or setinervals are "queued", whereas webcore is where JS code relating to the plugins run. It is the WebCore thread which stays alive, while the WebView thread is "dozed". Therefore, you cannot assume setTimeouts or setIntervals or even XHR's will execute while in the background. Remember that these constructs are "deferred" to the browser(WebView), and that you must write logic to handle situations where you need to work in the background.

same issue


Update travis config

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's Contributing Guide.
[ ] Rebase before creating a PR to keep commit history clear.
[ ] Add some descriptions and refer relative issues for you PR.

Coverage remained the same at 39.172% when pulling 92718b363c030e4a5f2a1d82928135e35ee9e2f8 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage remained the same at 39.172% when pulling 137345d001104f1a1aa89b0731317c5ff6cb554b on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage remained the same at 39.172% when pulling 8070a62d43b716709e7b988c963ff599244e6541 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage increased (+0.6%) to 39.726% when pulling ba6f033be38dec72a6cc0fa5a2158d9414bdabbb on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage increased (+0.6%) to 39.726% when pulling e8a784296bd8b12f900311107c9a6c81961d9a80 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling d9b85d95ca35fb697f85a5cfe6f9baa3a92c0761 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling 52d0dc476341c7427ec0dad0e89535a9dfa28b63 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling 6343e1aee01a19a93ab86775efcc7c8f838d0fcc on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling e8d62cece490f8a646e19b39d6718bb9b47fe02b on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling 765701804bf205108b82d62533b267ff532f4a1b on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.275% when pulling a645d2e2a70d430f9d2fa4d842758b2ca1747799 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.282% when pulling d7ddbcc01a7b88fcb1e2e9b004fd3a4c40f09e08 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.

Coverage decreased (-0.9%) to 38.282% when pulling c79c0355ab7496eb49cfdd5414b0396d09107a52 on QingWei-Li:feat/auto-build-dev into 8199c6ce766f7c0cf4e0ccf806b02441df42584f on ElemeFE:master.


Beginners Guide updates

Tonight is my first night trying to get EV3Dev and Lejos to play.  Sadly I am not a Linux or Maven expert
So
First issue
https://jabrena.github.io/ev3dev-lang-java/#/4/5
0.2 is not out yet and so anyone following this will get stuck
Second issue
I tried pasting the stuff listed on the github page,  etc in to my pom.xml and it did not like it.  I had to actually use one of the examples. (maybe its white space or something)
Third Issue
if you follow the example, your in a package called package ev3dev.examples.demo; (for nice website you have ev3dev.java.examples;)
You have a class called Test
but  your asked to run java -cp MyFirstRobot-1.0-SNAPSHOT.jar:ev3-lang-java-0.2-SNAPSHOT.jar ev3dev.java.MyFirstRobot.Test?
Where did MyFirstRobot come from?
Forth issue
Where is the ev3-lang-java-0.*-SNAPSHOT located, I do not have it on my machine anywhere (looking for 0.1 or 0.2)
Once we have a easy to follow guide I could do a youtube video?

Good morning Simon,
One:
yes, the release 0.2 is coming this week, I hope to release and you will see the .jar in https://jitpack.io
Two:
The example is on the repo.
If you download the repo, you could use the example:
git clone https://github.com/jabrena/ev3dev-lang-java.git
cd library
mvn package

later, move the jar generated to your brick with EV3Dev using a SFTP tool (For Example: Fillezilla) to path: /home
ev3-lang-java-0.2-SNAPSHOT.jar

To test the example is:
java -cp ev3-lang-java-0.2-SNAPSHOT.jar ev3dev.java.examples.Test

Third Issue
Once I release, all examples will be located here:
https://github.com/jabrena/ev3dev-lang-java/tree/master/examples
Not in the own library.
Forth issue
When you compile any project with maven, the default folder to store the java artifact (.jar) is ./target folder.

I did this document online:
https://jabrena.github.io/ev3dev-lang-java/
But I will create a guide with more detail with Jekill.

I will try this out hopefully this week :)

REJECTED BY LEAN


init deploy readme opt

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs

if too short, will be an error like : The signing key's size is 72 bits which is not secure enough for the HS256 algorithm.


in_array type error: Second argument ( $haystack ) must be of type array, null given.

Overview
Happening under PHP 8.1
TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in vendor/juanantoniodelgado/stopwords/src/Cache.php on line 64

#0 vendor/juanantoniodelgado/stopwords/src/Cache.php(64): in_array('pt', NULL)
#1 vendor/juanantoniodelgado/stopwords/src/Cache.php(39): StopWords\Cache->inHandlers('pt')

A downcast to array should fix it, me thinks.

but the actual problem is in the Indonesian language file, it reads "handler" instead of "handlers"

wait ... this seems to have been fixed fixed 2 years ago... then why composer installed it with the problem still there ? I am using 1.3

My apologies, but it seems that we never released a new version with the fix on Packagist. This has been fixed now by releasing 1.4.


Document comments format in _headers

In the _headers documentation, I could not find how to do comments.
I've asked on Discord, and verified the answer.
I also noticed that _redirects lacks the same documentation, and though I suspect the syntax is the same, I did not verify that.

Hmm, there is a small typo: "on a separate lines". The 'a' should be removed.

Hey, thank you for this! Instead of adding an entire section just for this, can you add a single comment around L30? That should be enough for people to realize how to do them.
Something like this:
---
filename: _headers
---
# This is a comment
/secure/page
  X-Frame-Options: DENY
  X-Content-Type-Options: nosniff
  Referrer-Policy: no-referrer
/static/*
  Access-Control-Allow-Origin: *
  X-Robots-Tag: nosnippet
https://myproject.pages.dev/*
  X-Robots-Tag: noindex

@lukeed Good suggestion, implemented.


Livepeer Explorer: Call history to exclude current round

What's the problem? (required)
Currently the call history in the Explorer includes the current round, if an Orchestrator waits for lower gas fees during the round the call history shows 29/30 until it is called.
This is misleading because the O could still call every round and still be redeeming 30/30 when it shows 29/30.
This can confuse delegators and hinder Os from receiving stake because they do not call reward immediately each round.
Solution
Do not include the current round in the trailing 30 day history.

Any update on this?
Would love to see the implementation of this while gas fees are high.
Sitting at 29/30 when calling every round may put good operating Os at a disadvantage to Os with deep pockets that call at the beginning of each round regardless of price.
Cheers!

Thanks for flagging @Titan-Node! A fix has been deployed 🚀. Call history now excludes the current round.


[HUDI-7229] support partial updates for cdc payload demo

Change Logs
Use MysqlDebeziumSource as an example to demonstrate the design.
Impact
Low.
Risk level (write none, low medium or high below)
None, just a demo.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

This is not a correct direction for cdc demo.


Describe ingress controller network options

https://github.com/rancher/docs/issues/3297

i tried to configure ingress-nginx with metallb loadbalancer IP today in my lab and found out that "publish-service" extra also needs to be set for the ingress ressource.
otherwise all the ingress objects will have the node ip as address, which causes issues when using external-dns
this is my config which solves all that
  ingress:
    default_backend: false
    extra_args:
      http-port: '80'
      https-port: '443'
      publish-service: $(POD_NAMESPACE)/ingress-nginx-controller
    http_port: 0
    https_port: 0
    network_mode: none
    provider: nginx


Implement current API as per O-RAN Spec

calling currentstate via api with endpoint /resource/CurrentState
This PR only has changes to support CurrentState call from HTTP only.
AMQ implementation will be in separate PR
Signed-off-by: Aneesh Puttur<EMAIL_ADDRESS>

holding for Jack to review before we merge


Default Sorts on EA Type

As a team member
I want a default sort on the Resource Forecast
so that I can easily see and prep the Resource Forecast for export
Acceptance Criteria
Scenario 1:
GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)
Scenario 2:
xxxxxx
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

EA Type -> Project Name ( Sort )


OwlReadyOntologyParsingError: NTriples parsing error (or unrecognized file format) in knowledge_graph.ttl.

I am facing a parsing error when using ontolearn. The XML format of the same Knowledge Graph was successfully parsed but not the turtle format.

Would be very helpful if could you add some context like the code you are executing, and the error that is occurring.


deselect if clicked anywhere in master content

Is there no better way than to call event.stopPropagation() on all elements that need to be clicked but live in the master-content?

Is there no better way than to call event.stopPropagation() on all elements that need to be clicked but live in the master-content?

The problem is that an click will not only fire the "nearest" handler. if you layer multiple handler over each other all of them will be triggered. That's how the browser works.
So the only way you can prevent this is with the stopPropagation or by not stack handler over each other


Incompatible with latest rate-limit-redis RedisStore

The exported object RedisStore, of npm module rate-limit-redis does not have property incr. Even if I change the name from increment to incr it gives run time error.

For now, you should go with the older version of rate-limit-redis.
This project should get updated to support the new API, but that is going to be a fairly involved process and won't happen very quickly.

@nfriedly The problem here is that your other package https://github.com/nfriedly/express-rate-limit is compatible with latest version of rate-limit-redis  and make it very uncomfortable to use both library in a same project if we want latest version on each of them :/
Maybe i can help to make it usable for both old and new api of store ?

Well, the latest version express-rate-limit is backwards compatible with the older version of rate-limit-redis, so that shouldn't be an issue. rate-limit-redis is the only one you'll need to pin to an older version for now.
But, yes, if you can update express-slow-down to support the newer API, I would appreciate that.
The roadmap in my mind was to fix up the test reliability first, and then update the API, possibly converting to typescript at the same time as the API update. That's the basic path we took for express-rate-limit.

Step 1 is done - we now have full test coverage across windows, mac, and linux with multiple versions of node.js tested on each.
I'm toying with the idea of rebuilding express-slow-down on top of express-rate-limit, essentially as just a custom handler callback that delays the request instead of responding with an error page. I think it would solve the store compatibility issue once and for all, while at the same time making this repo smaller and simpler.

@nfriedly i couldnt agree more about your idea of rebuilding express-slow-down into express-rate-limit, that would make things way easier to handle with only one package to use by everyone. After all slowing down request usually go with rate limit

when this could be solved? it does not work out of the box, maybe there is some glue code someone have?

Thanks to @AdrianoRuberto v1.6.0 now has support for the newer promise-based Store API that express-rate-limit now uses. It should also retain backwards compatibility with older stores.
Please test it out and let me know if you run into any issues.


Crash after stopping recording

when i click button to start recording, everything is ok.  but when i click button to stop recording , the app was crashed.

solution is in #46 ,  not #57 。 it's worked for me

From startPreview(), comment out closePreviewSession();
private void stopRecordingVideo() {
// UI
mIsRecordingVideo = false;
mButtonVideo.setText(R.string.record);
// Added by Ben Ning, to resolve exception issue when stop recording.
try {
mPreviewSession.stopRepeating();
mPreviewSession.abortCaptures();
} catch (CameraAccessException e) {
e.printStackTrace();
}
// Stop recording
mMediaRecorder.stop();
mMediaRecorder.reset();
    Activity activity = getActivity();
    if (null != activity) {
        Toast.makeText(activity, "Video saved: " + mNextVideoAbsolutePath,
                Toast.LENGTH_SHORT).show();
        Log.d(TAG, "Video saved: " + mNextVideoAbsolutePath);
    }
    mNextVideoAbsolutePath = null;
    startPreview();
}

This sample has been migrated to a new location (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


[Security] Static IV during encryption/decryption

Came from https://mcndt.dev/posts/how-to-e2e-encryption/ 👋🏻
Describe the bug
Currently the code sets the IV to static value of 0s, and this is considered to be insecure.. Consider randomizing your IVs.
https://github.com/mcndt/obsidian-quickshare/blob/73733c0292cb3f0d6775c69c734e80c690932777/src/crypto/crypto.ts#L45-L49
https://github.com/mcndt/noteshare.space/blob/f84ddba528b73c160a16b707ede064b752d3528a/webapp/src/lib/crypto/decrypt.ts#L54-L59
Also, please consider reading https://security.stackexchange.com/a/17046 with regards to secure usage of AES-CBC on your service. I honestly think it's better off to do something with GCM than with CBC mode.

Hi!
I appreciate your work vetting the security of the quickshare plugin.
I chose to use a static IV of 0 because keys are never reused. Are there still vulnerabilities in that case? Would love to learn more.
I will consider making a v3 implementation of the crypto suite using these recommendations (switch to GCM, #20 random keys) soon.

I assume it could be reasonably safe since the keys are being reused only for once, at least for now.
However, if the plaintext of the first block is known, the attacker can still bruteforce to find out the value of the key. Unfortunately, I also assume this kind of attack scenario to be not that practical since the key is in 256bit.
I think there's only encryption of markdown text for the current specification, so it's very unlikely that the attack will be successfully achieved. But if the project is planning to extend to contain files or images, the plaintext of first block could be known because of the image headers, which makes it possibly easier to find out the key of the encrypted content.
Wouldn't it better off to share the randomized IV along with the decryption key?

Yeah when I update the encryption I will do so.

Shipped in version 1.0.2!
Feel free to have another look at the code if you want to check again for problems.
If I may ask, how did you stumble across my blog?

I will check later when I have time. I just checked your post from reddit. Thanks for updating!


Support (asynchronous) cookie jars

As pointed out by @z3nful in https://github.com/gadicc/node-yahoo-finance2/pull/667#issuecomment-1716757932, we really shouldn't need to fetch a new cookie on every new startup.  This is especially an issue for serverless functions which are short-lived.
This has always been the plan; file-system and even database storage.  The slightly more time consuming challenge is the initial cookie code was all programmed as synchronous calls, so it requires a little more work to change the whole flow to work asynchronously.
Leaving this open for now but anyone else is welcome to take a look too.  Since we use https://www.npmjs.com/package/tough-cookie internally, we should just support any of their async cookie stores.  However, we may need some async bridge code to ensure everything is set up correctly and in the correct order.

[X] Make all cookie code async - https://github.com/gadicc/node-yahoo-finance2/commit/280007ecb151e81631d652df43a5e008190da6da
[X] Ability to specify custom cookiejar with custom cookie store - https://github.com/gadicc/node-yahoo-finance2/commit/b298844f2fdd848e18473261e4d9cf4666ee5f30
[x] cookie / crumb expire times
[ ] invalid cookie / crumb error handling?
[x] Documentation
[ ] Tests

Bad gadicc!  This should have all been in a separate branch / pull request, not separate commits.  My apologies :sweat_smile:

Shippable.  The missing items aren't related to this feature specifically, but in getCrumb in general, and should be addressed elsewhere.


Fix Docs Dockerfile packages

Description of changes:
Updates the docs Dockerfile to include all necessary OS packages for the Python packages it uses
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Location field of ResourceGroup is required

Description of your changes
API returns error if location is not given:
'create failed: cannot create ResourceGroup: resources.GroupsClient#CreateOrUpdate:
      Invalid input: autorest/validation: validation failed: parameter=parameters.Location
      constraint=Null value=(*string)(nil) details: value can not be null; required
      parameter'

Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation, examples, or release notes.
[x] Updated the dependencies in app.yaml to include any new role permissions.

looks like the composition in the quick start will need to be update

I don't think so. We just add a validation here to reject the creation without that field. If it's there in the composition, it should work as expected.


docker-credential-osxkeychain error on OS X

Getting this error with TestContainer 1.9.1 (reproduced on 1.9.0 as well)
2018-10-15 11:18:43.097 [main] ERROR o.t.s.o.z.exec.ProcessExecutor -  - Could not start process:
java.io.IOException: Cannot run program "docker-credential-osxkeychain": error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.invokeStart(ProcessExecutor.java:1016)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.startInternal(ProcessExecutor.java:989)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.execute(ProcessExecutor.java:925)
	at org.testcontainers.utility.RegistryAuthLocator.runCredentialProgram(RegistryAuthLocator.java:323)
	at org.testcontainers.utility.RegistryAuthLocator.runCredentialProvider(RegistryAuthLocator.java:219)
	at org.testcontainers.utility.RegistryAuthLocator.authConfigUsingStore(RegistryAuthLocator.java:186)
	at org.testcontainers.utility.RegistryAuthLocator.lookupAuthConfig(RegistryAuthLocator.java:120)
...

when revert back to 1.8.3 version - everything starts working again and I don't see this error anymore.

Hi Toly,
Hopefully we can resolve this - could you just check a few things?

If you look at your ~/.docker/config.json file do you see osxkeychain mentioned there as a credential store or credential helper?
Do you have a program named docker-credential-osxkeychain on your system anywhere? Is it on your PATH? (FWIW it is a standard part of the Docker for Mac installation so should be there somewhere)
Do you actually need to pull images from a private docker registry, or are you only using public images?

Thanks
Richard

Hi Richard, thanks for such a quick reply. As I mentioned previously - it started to break only with 1.9 version and yes - I do have "docker-credential-osxkeychain" in my path (I can run it in terminal). I took a look at config.json as well:
{
  ...
  "credsStore" : "osxkeychain"
}

I use public images.

That is very strange - please could you try dumping the PATH as seen by the Java process (e.g. grab the value of System.env("PATH") somewhere in your test code).
The error implies that this executable is not in a place where Testcontainers can find it.
As a short term fix you could try removing the credsStore line from your docker config file; this would stop Testcontainers from trying to use it. I'm not sure if the line would automatically be reinstated later or not, though, so this isn't a long term fix.

Interesting. So it does not look like a TestContainers problem. I tried System.getenv("PATH") and it returns null on my Mac. This is weird, have to investigate it. So what I did is added PATH="/usr/local/bin/" in IntelliJ's Run Configuration and it is started to work. Thank you so much for System.getenv("PATH") hint, still have no clue why it returns null on my computer but at least I'm unblocked with using TestContainers 1.9.1. BTW, do you have any idea why it works on 1.8.x setup?

I do get a very similar exception on Windows:
java.io.IOException: Cannot run program "docker-credential-": CreateProcess error=2, Das System kann die angegebene Datei nicht finden
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.invokeStart(ProcessExecutor.java:1016)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.startInternal(ProcessExecutor.java:989)
	at org.testcontainers.shaded.org.zeroturnaround.exec.ProcessExecutor.execute(ProcessExecutor.java:925)
	at org.testcontainers.utility.RegistryAuthLocator.runCredentialProgram(RegistryAuthLocator.java:323)
	at org.testcontainers.utility.RegistryAuthLocator.runCredentialProvider(RegistryAuthLocator.java:219)
	at org.testcontainers.utility.RegistryAuthLocator.authConfigUsingStore(RegistryAuthLocator.java:186)
	at org.testcontainers.utility.RegistryAuthLocator.lookupAuthConfig(RegistryAuthLocator.java:120)
	at org.testcontainers.dockerclient.auth.AuthDelegatingDockerClientConfig.effectiveAuthConfig(AuthDelegatingDockerClientConfig.java:43)
	at com.github.dockerjava.core.DockerClientImpl.createContainerCmd(DockerClientImpl.java:316)
	at org.testcontainers.dockerclient.AuditLoggingDockerClient.createContainerCmd(AuditLoggingDockerClient.java:32)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:255)
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:237)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:76)
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:235)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:220)

I do have a default Hyperv-based installation with no customizations so far. My config looks like:
{
  "credsStore": "",
  "auths": {},
  "stackOrchestrator": "swarm"
}

This is interesting - I'd say that "credsStore": "" is not valid... But regardless of whether it's valid or not, it's occurring in more than one place so probably has a systemic cause.
We should guard against this.
I don't have much time right now, but maybe someone could contribute some extra validation to RegistryAuthLocator to prevent an empty string being used for a credential store / credential helper?

Same for me in Eclipse on Mac. Testcontainers 1.10.6. No Exception with version 1.7.3. Printing the PATH returns /usr/bin:/bin:/usr/sbin:/sbin

For OSX users, who is using Docker desktop:

make sure to uncheck Securely store Docker logins in macOS keychain
OR store your credentials in keychain properly.

Merged #1303 to fix this.

I see the same problem.. my ~/.docker/config.json contains:
"credsStore" : "osxkeychain",
"credSstore" : "osxkeychain",

@cschneider
I investigated the behaviour of docker desktop:

check box Securely store Docker logins in macOS keychain -> "credSstore":"osxkeychain" automatically created by docker desktop, then I checked Keychain Access, searched for docker, I was able to see newly created credentials. Run integration tests -> all ok
uncheck box -> "credSstore":"", docker desktop also remove docker credentials from Keychain Access. Run integration tests -> all ok
I manually removed whole field "credSstore":"" from .docker/config.json. Run integration tests -> all ok

I think this issue relates to docker desktop application, not testcontainers.
some screenshots:

Releasing #1303 in 1.11.0 🎉

@NikitaZhevnitskiy good investigation - that "credSstore" is bizarre! Maybe worth reporting this over in https://github.com/docker/for-mac ?
I'm going to close this ticket now that we're releasing a workaround, but if this problem recurs in any way from 1.11.0 onwards please open a new issue and link this one.

add the directory contains the docker-credential-desktop to PATH Env.

I solved it by remove credsstore

I solved it by remove credsstore


The problem of video, audio crashing of certain websites persists

It seems to be a specific problem with Google's core browser and Realtek sound card, and sometimes it is caused by the browser, sound card driver, and core graphics card driver. For this problem, regardless of whether the core version number is up to date, the Firefox browser is not seriously affected. Then, I have an idea; since it is based on the chromium open source project, can you absorb and expand your team from outstanding contributors? woes with the upstream version); longing for Th builds to get strong and return to the upstream version. Or there are enough people to open the official version, Beta, DEV, and Canary four update channels. Thanks!

The following movies are not provided separately: the browser plays these videos to one-third of the movie Jiutianxuandijue, Ghost Slayer: One Piece, Quenhuo Danxin, God's Tomb, Zhu Xianzhuan, audio abnormality, picture freezing; blue screen of death

No crashes have been found in local testing for the time being. You will need to provide the URL of the website where the crash occurred and the relevant crash information, as well as details of your system environment and browser version number.
Currently, the development of the Thorium browser is advancing in an orderly manner. We will not rush to follow up with new versions, and we may not consider opening other branches.
In addition, since your previous feedback failed to form an effective communication with us, if you still fail to provide the information I requested after this reply, I will close this issue.
@whxuezhe

@gz83 I have a blue screen log on the Vision Forum in China, please analyze it.https://bbs.pcbeta.com/viewthread-1971748-1-1.html
System environment win11 25393.1000 Realtek ALC862 integrated sound card, <IP_ADDRESS>17 sound card driver, core display driver <IP_ADDRESS>99 browser core is Th build 113 and Chrome116 CPU i9-12900H 3080Ti Laptop Browser video playback calls the core graphics card

So is it a crashing problem or a blue screen that you want feedback on?
Also, I am not obliged to analyze the blue screen logs for you.
@whxuezhe


Make ODYM pip installable

This pull request makes ODYM pip installable, as I found this easier to work with.

Merged this without review as it only affects my own fork.


winch: Overhaul the internal ABI

This change overhauls Winch's ABI. This means that as part of this change,  the default ABI now closely resembles Cranelift's ABI, particularly on the treatment of the VMContext. This change also fixes many wrong assumptions about trampolines, which are tied to how the previous ABI operated.
The main motivation behind this change is:

To make it easier to integrate Winch-generated functions with Wasmtime
Fix fuzz bugs related to imports
Solidify the implementation regarding the usage of a pinned register to hold the VMContext value throughout the lifetime of a function.

The previous implementation had the following characteristics, and wrong assumptions:

Assumed that internal functions don't receive a caller or callee VMContexts as parameters.
Worked correctly in the following scenarios:

Wasm -> Native: since we can explicitly load the caller and callee VMContext, because we're calling a native import.
(Native, Array) -> Wasm: because the native signatures define a tuple of  VMContext as arguments.

It didn't work in the following scenario:

Wasm -> Wasm: When calling imports from another WebAssembly instance (via direct call or call_indirect. The previous implementation wrongly assumed that there should be a trampoline in this case, but there isn't. The code was generated by the same compiler, so the same ABI should be used in both functions.

This change introduces the following changes, which fix the previous assumptions and bugs:

All internal functions declare a two extra pointer-sized parameters, which will hold the callee and caller VMContexts
Use a pinned register that will be considered live through the lifetime of the function instead of pinning it at the trampoline level. The pinning explicitlly happens when entering the function body and no other assumptions are made from there on.
Introduce the concept of special ContextArgs for function calls. This enum holds metadata about which context arguments are needed depending on the callee. The previous implementation of introducing register values at arbitrary locations in the value stack conflicts with the stack ordering principle which states that older values must always precede newer values. So we can't insert a register, because if a spill happens the order of the values will be wrong.

Finally, given that this change also enables the imports.wast test suite, it also includes a fix to global.{get, set} instructions which didn't account entirely for imported globals.

Oh bad rebase -- sorry about that. Fixing it now.


Create reference SAML federation method i Authentik against OIOSAML3.0

Docs:
general: https://digitaliseringskataloget.dk/løsninger/adgangsstyring-brugere
.net: https://github.com/kombit/tokenservice_oioidws-net/blob/main/README.md
Danish config guide (tied to the node.js implementation):
https://os2iot.readthedocs.io/en/latest/kombit-adgangsstyring/kombit-adgangsstyring.html
Node.js project:
https://github.com/node-saml/passport-saml
Reference code in java and .net:
https://digst.dk/it-loesninger/standarder/oiosaml-profiler/
https://github.com/digst/OIOSAML.Net
https://github.com/digst/OIOSAML.Java
A saml provider in Go by KvalitetsIT:
https://github.com/KvalitetsIT/gosamlserviceprovider
Gosaml2: https://github.com/KvalitetsIT/gosaml2

@nicolas-semaphor
test server os2-test-ak runs the development version of Authentik where @nicolas-semaphor is working on the SAML source including its library of "processors" which is responsible for generating metadata, sending and extracting SAML authn requests and folder to AK users
@nicolas-semaphor  is currently working on sending an AuthnRequest to FKIS, which it will accept, to encrypt the package properly.

Reference implementation will be a custom connector for Authentik with OIOSAML3.0
The hope is that the encryption code improvements will be accepted upstream.

Can this be considered 100% complete @nicolas-semaphor ?

Closing as solved @nicolas-semaphor, please create a new issue and add it to a future milestone if this is only partly solved.


Firefox gets 'stuck' while starting for the first time

When starting Firefox from the GNOME dock on a new login session, it gets 'stuck': there are firefox processes running (and starting Firefox again correctly gives the 'firefox is already running but not responding' error). After killing it, starting it again seems to work fine.
I can reproduce this fairly reliably on a newly-installed NixOS unstable machines with GNOME. (I don't see it on my regular development laptop with NixOS unstable and sway, though)
/cc @hexa @lovesegfault

I'm pretty certain I've had this issue before, both on GNOME with Wayland.
Have you tried using the environment variables: MOZ_ENABLE_WAYLAND=1 and XDG_CURRENT_DESKTOP=sway ?
You can find more about them here: https://nixos.wiki/wiki/Firefox (Scroll to the bottom of the section labelled Wayland)

this may no longer be happening on latest nixos-unstable (897876e4c484f1e8f92009fd11b7d988a121a4e7), at least on one new machine it seemed fine. Closing for now.


fix: include config callbacks in batch render

:tada: This PR is included in version 2.21.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug: oneOf type makes field required

Current behavior:
The oneOf type makes a field required.
Proper behavior:
The oneOf type should make no changes to the required state of the field.
Explanation:
The oneOf type is a variation of subschema boolean logic. It's difference to anyOf which works properly in enjoi is that an instance should match exactly one of the subschemas. If it matches two or more - validation fails. But this is only if the instance value is present. That is, if the field is oneOf, but is not included as a required field it should pass validation.

Actually the unit tests for oneOf are quite limited and do not cover all the scenarios. I recommend you prove your rightfulness by writing good tests.


New token validation path: Renamed result types

New token validation path: Renamed result types
Updated the type names for the new token validation path to prevent future clashes with the type name "Result".
ValidationResult -> ValidatedToken
ExceptionDetails -> ValidationError
Result -> ValidationResult
Validators and delegates now return ValidationResult.
ValidateTokenAsync now returns ValidationResult<ValidatedToken>
Failed validations now return a ValidationError within UnwrapError()
Part of #2711

Git did a whole mess due to the fact that I renamed a different file to the name that a previous one had. So now it is comparing OldA against newB.
This PR made no changes to the renamed types, only to the references in other files.


Incorrect no-super-linear-move report with a lookbehind assertion

Information:

ESLint version: 8.30.0
eslint-plugin-regexp version: 1.11.0

Description
The rule regexp/no-super-linear-move: "error" reports the error below:
/(?<=^a*)b/;
// Any attack string /a+/ plus some rejecting suffix will cause quadratic runtime because of this quantifier
// regexp/no-super-linear-move

This does not seem correct, because there is already a ^ assertion.

Sorry for my misunderstanding. It is quite interesting that rewriting the regular expression  as /^(a*)b/ will be a lot faster.

Yes, that's because the regex engine matches /(?<=^a*)b/ left to right and character by character.
Example: Given the string aaa, it will start at position 0 and go into the lookbehind, which will match, only to find that there is no b as position 0. At position 1, the lookbehind will match 1 a, but there is still no b, so on to the next position. At position 2, the lookbehind will match 2 as, but this still no b, at position 3, the lookbehind will match 3 as, but still no b. And then we have already reached the end of the string. We found no matches, so the string aaa is rejected.
The key insight is that at each position, the regex engine must go through O(n) many as to match the lookbehind. Since there are n position in a string of length n, and each position takes O(n) time to match, the total runtime is O(n^2).
Unfortunately, browser regex engines don't do a lot of optimization on the pattern itself and will interpret it pretty much literally. In particular, this regex could have had linear runtime of the regex engine had been smart enough to see that checking for b first ( O(1) ) and then going into the lookbehind ( O(n) ) is a lot faster.
But on the upside, the lack of such optimizations makes writing algorithms for detecting these worst cases a lot easier :)

Also, you solved the problem with a capturing group, which works great, but if you must use a lookbehind, you could also do this: /b(?<=^a*b)/.
A bit hacky, but it does work. Note that this isn't a general workaround like capturing groups. This only works when both a and b are single characters (or character sets, or character classes), and a and b are disjoint (they are different characters/there is no character accepted by both).
So keep using capturing groups if you can. There are simply fewer surprises with them.

@RunDevelopment Thank you so much for your detailed explanation and a surprising solution!


Missing Experiments in README file

Following experiments are not placed in README file although there documentations are available in experiments folder

Capacitor Discharging

Linear Ramp Generator

Electromagnetic Induction

Piezo Buzzer

Ultrasonic Range Finder

Transient RLC Response

Piezo Bandwidth Characteristics

RC Integrals, Derivatives

@harsh-2711 can i work on this ?

@ananyaarun  I have made the PR and it will soon be accepted after I do proposed changes, So, you can better work on other issue


ERROR: bucket overflow

I occasionally get the following error for the code that normally works.

An observation that may or may not be relevant: I noticed that this error seems to occur when the number of coordinates in the sparse tensor is small. The same code ran fine without producing the above error when a bigger input with more coordinates was fed.

Could you provide us with a sample code and data that can reproduce this error? Thanks!

As of now, my program is quite big (involving multiple files) and the error occurs only occasionally. So, I am not in a position to provide simple sample code to reproduce this as of now. Let me try investigating this and see whether I can narrow it down.
As of now, if anybody has any insights about what could potentially cause those errors, that can help my investigation.
Thanks.

I found out the limitation in the code that is causing this.
In query.cpp, the following line is used to compute the size of the table:
int table_size =  2 * pow(2,ceil(log2((double)n)));
In hashmap.cuh, the number of buckets is computed to be table_size/BUCKET_SIZE, where BUCKET_SIZE is 512.
When the hash values of the coordinates are very distributed there is no problem. Taking the table_size to be 2 times next power of 2 greater than n, as done in the line above provides some amount of tolerance for the case where the hash values are not evenly distributed. But, that is only a heuristic. When the hash values are more un-evenly distributed than that, the code fails with the "ERROR: bucket overflow!" messages.
I was able to avoid the error in my specific case by changing "table_size = 2 * blah" to "table_size = 3 * blah". But, of course this is not a real solution of course. It is just a hack that increases the tolerance for unevenness some more.

For the benefit of others running into this, let me mention how I addressed it for now. There used to be the following line in query.cpp:
int table_size = 2 * pow(2,ceil(log2((double)n)));
I replaced it by:
  const int nextPow2 = pow(2,ceil(log2((double)n)));
  // When n is large, the hash values tend to be more evenly distrubuted and choosing table_size to be
  // 2 * nextPow2 typically suffices. For smaller n, the effect of uneven distribution of hash values is more
  // pronounced and hence we choose table_size to be 4 * nextPow2 to reduce the chance of bucket overflow.
  int table_size =  (n < 2048) ? 4 * nextPow2 : 2 * nextPow2;

This way, for larger n, when memory size consideration is more important, the table_size is getting computed to be the same as it used to be. For smaller n, when the effect of uneven distribution of hash values is more pronounced and memory size consideration is not as important, we compute the table_size to be bigger than it used to be, to reduce the chances of bucket overflow error.
Original authors: I will submit a pull request with this change. But, I won't be offended :-) if you reject this pull request since this change just reduces the chances of the bucket overflow error and doesn't address the issue in a robust, thorough way.

@victoryc, thank you so much for investigating this issue! I was discussing with @kentangSJTU this morning about the same solution. I will be happy to take a look after you submit the PR. We are also thinking about making this a knob to tune so that users can change that based on their needs. Take one step further, it might also be possible to dynamically adjust this if there is overflow.

Hi there,
I am getting the same error. Are you still planning on adding a knob to tune?
Cheers,
Harry

Hi @harry1576, it's not in our plan for the near future. As a workaround, you may follow https://github.com/mit-han-lab/torchsparse/issues/55#issuecomment-815981257 to enlarge the table size further.

Please I followed through the suggestions for this issue, but that did not fix it.  Is there an alternative solution to this problem.


Junk written to stdout

Something is emitting an AST to stdout. For some reason it only happens in production (and it's breaking our deployment script, which uses stdout to pipe Browserify's output through the Google Closure compiler). Any idea what this could be? This is after a clean npm install.
./node_modules/.bin/browserify -t 6to5ify --extension .jsx app/bundles/app.js --outfile /dev/null
{ type: 'XJSOpeningElement',
  start: 1707,
  end: 1732,
  loc:
   { start: { line: 61, column: 6 },
     end: { line: 61, column: 31 } },
  range: [ 1707, 1732 ],
  attributes:
   [ { type: 'Property',
       kind: 'init',
       key: [Object],
       value: [Object],
       computed: undefined,
       loc: [Object],
       end: 1731,
       range: [Object],
       start: 1716,
       leadingComments: [],
       trailingComments: [] } ],
  name:
   { type: 'Identifier',
     start: 1708,
     end: 1715,
     loc: { start: [Object], end: [Object] },
     range: [ 1708, 1715 ],
     name: 'section' },
  selfClosing: false }
[... lots more output ...]

Our shrinkwrap file, in case it helps: https://gist.github.com/atombender/2c1d523bc362324d3b7d.

Looks like this is caused by the 6to5/6to5 lib itself. I've opened a pull request to remove the log (6to5/6to5#469)

Looks like it. Thanks, reverting to an earlier version in the meantime.

Ugh, sorry!


config: introduce the configuration package

Move the config logic, currently handling the configuration flags, into a proper package. Benefits of this move:

better testability
enable code reuse
enable future refactorings/changes
open the opportunity for code simplification
allows us to take the chance to rewrite the unit tests, shedding a dep - we should really use the simple testing package here unless  something more powerful is clearly needed.

need to come after (and be rebased on top of ) https://github.com/k8stopologyawareschedwg/resource-topology-exporter/pull/120

/lgtm

/approve


Rename LICENSE.txt to LICENSE

@fir3pho3nixx

What about the LICENSE.txt file?

Was renamed to LICENSE (no extension).

I see. My bad :)


Change MACOSX_DEPLOYMENT_TARGET

For Py3.7
See if it fixes breaking CI. I'm not sure why it's only failing for one Python version though

I think Github created this branch on the main repository which wasn't what I intended to do. I'll try to avoid this next time.

Does at least look to have fixed the failing test though...

Thanks


Update dev dependencies

I was playing around with snyk and found
https://snyk.io/vuln/npm:uglify-js:20151024. We depend on uglify
through istanbul (dev only) so it shouldn't matter but
updating is always good as are green badges.

@ofrobots PTAL.

LGTM.


Recipe roll failing due to bot_update getting bytes

https://flutter-review.googlesource.com/c/recipes/+/25641
Traceback (most recent call last):
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 1225, in <module>
    sys.exit(main())
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 1209, in main
    checkout(options, git_slns, specs, revisions, step_text)
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 1111, in checkout
    synced_solutions = ensure_checkout(**checkout_parameters)
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 648, in wrapper
    return fn(*args, **kwargs)
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 838, in ensure_checkout
    synced_solutions = git_checkouts(
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 658, in git_checkouts
    did_sync = _git_checkout(
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 705, in _git_checkout
    git(*populate_cmd)
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 278, in git
    return call(*cmd, **kwargs)
  File "C:\b\s\w\ir\kitchen-checkout\depot_tools\recipes\recipe_modules\bot_update\resources\bot_update.py", line 234, in call
    buf = '\r' + buf
TypeError: can only concatenate str (not "bytes") to str

This seems to be a windows specific issues

This is potentially due to p2 vs py3 differences in handling of bytes and strs.
Depending on args to subprocess.Popen, buf could be bytes or str, which will cause issues with trying to concatenate the str to bytes if (e.g. '\r' + buf).
buf would needed to be decoded if its a byte stream.

As per @CaseyHillers , looks like the error is due to a py3 issue.
The change was was reverted: https://source.chromium.org/chromium/chromium/tools/depot_tools/+/6bfbe35cce2380773e38bd622b35caed86d8aec0
So closing this issue.


[Caching] Create clang importer from cc1 args directly

When caching build is enabled, teach dependency scanner to report command-lines with -direct-clang-cc1-module-build so the later compilation can instantiate clang importer with cc1 args directly. This avoids running clang driver code, which might involve file system lookups, which are the file deps that are not captured and might result in different compilation mode.
rdar://119275464

Currently, only enable the new code path when caching is enabled since it is quite a big behavior change. Caching build requires the change since its restricted file system will definitely alter the behavior for clang importer. For normal explicit module build, this will still help with less lookup during the actual compilation, but we can enable that later.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Rebase to resolve conflict. After some extensive testing, I feel pretty confident to turn this on for caching only. Ready to be reviewed.
@artemcm @DougGregor @benlangmuir @beccadax Since this is a pretty big behavior change, do you have any concern turn on this for all explicit module build? Will run a separate qualification for that.

Rebase to resolve conflict. After some extensive testing, I feel pretty confident to turn this on for caching only. Ready to be reviewed.
@artemcm @DougGregor @benlangmuir @beccadax Since this is a pretty big behavior change, do you have any concern turn on this for all explicit module build? Will run a separate qualification for that.

Given sufficient qualification I don't have a concern with enabling this for all Explicit Module Builds. But it would be good to have that enablement be a separate change after this one that we hold off merging until we're able to get enough confidence/validation, or land behind a flag temporarily which we can use to do testing with.

Since this is a pretty big behavior change, do you have any concern turn on this for all explicit module build? Will run a separate qualification for that.

Doing this for all explicit builds seems best to me.  Not only this reduces the differences in behaviour for caching, but it also means that clang modules used by swift will behave more like clang modules used by clang -- clang's dependency scanner has been using -cc1 for explicit module builds for a while now.

But it would be good to have that enablement be a separate change after this one that we hold off merging until we're able to get enough confidence/validation, or land behind a flag temporarily which we can use to do testing with.

Flag seems like a good idea to me to make it easier to control until we're ready to flip the default for non-caching.

Add a flag to turn on this new behavior for non-caching build. Add some nice to have swift-driver support here: https://github.com/apple/swift-driver/pull/1550

@swift-ci please smoke test linux platform

@swift-ci please smoke test

Rebase to resolve merge conflict. Still waiting for review :)

@swift-ci please smoke test

ping~

@swift-ci please smoke test

@swift-ci please smoke test

@artemcm Ping. Most of the PR should have no changes to non-caching build unless the new option is explicated used. The only behavior changing part is separated out as 9f736811f0a6bdc87b5af81dce00929a48fb0673. Let me know if this is good to merge as I have lots of other patches that can cause conflict with this one.

I am trying to find the reason for an internal failure in a Linux system. For it to work, we need to provide Clang with --gcc-toolchain=/foo/bar to point to the GCC toolchain in a non-standard location, so we normally use -Xcc --gcc-toolchain=/foo/bar. It seems that this PR might forward that parameter (which is intended for the Clang driver) to cc1, failing many of the tests with unknown argument: '--gcc-toolchain=/foo/bar' … error: clang importer creation failed.
Is there a way of still using the Clang driver or is that completely gone? Is there a good place to filter then non-cc1 arguments somehow? I am not sure that removing --gcc-toolchain from the command lines will work at all, since it expands to many search paths and options (and I can imagine some other similar options that the Clang driver expands to many options in cc1).

I am trying to find the reason for an internal failure in a Linux system. For it to work, we need to provide Clang with --gcc-toolchain=/foo/bar to point to the GCC toolchain in a non-standard location, so we normally use -Xcc --gcc-toolchain=/foo/bar. It seems that this PR might forward that parameter (which is intended for the Clang driver) to cc1, failing many of the tests with unknown argument: '--gcc-toolchain=/foo/bar' … error: clang importer creation failed.
Is there a way of still using the Clang driver or is that completely gone? Is there a good place to filter then non-cc1 arguments somehow? I am not sure that removing --gcc-toolchain from the command lines will work at all, since it expands to many search paths and options (and I can imagine some other similar options that the Clang driver expands to many options in cc1).

The new option is supposed to be only used for explicit module build, which requires dependency scanning. The -Xcc command passed to the swift-driver (or swiftc) is still clang driver flag and that has not changed. There has always been a special mode (mostly for building PCM) that changes the meaning of -Xcc flag to swift-frontend to be clang cc1 flag, from which you have to provide all the arguments to initialize clang importer. This patch just add a new option to ask swift dependency scanner to return options to initialize all swift-frontend directly with cc1 options.
There is a follow-up PR in swift-driver to tell it not to forward -Xcc option from the command-line to swift-frontend anymore. https://github.com/apple/swift-driver/pull/1550. It doesn't need to be forwarded because swift dependency scanner has already seen the driver flag and created the list of cc1 flag that is corresponding driver options and swift-frontend does not need to run clang driver again.


VS 2017 compatibility

The article does not explicitly mention that the CRM SDK templates for visual studio only support VS 2012, 2013 and 2015 and NOT Visual Studio 2017. This is, IMHO a HUGE deal for most developers; it's the latest stable version of Visual Studio and it is not supported. I think this should at least be mentioned at the beginning of the article.

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

ID: e23f37d6-4060-e582-9be9-e50dc3fe8917
Version Independent ID: 439c7dc9-8b94-8abd-45e9-0987fe3cee3b
Content: Create packages for the Dynamics 365 for Customer Engagement Package deployer (Developer Guide for Dynamics 365 for Customer Engagement apps)
Content Source: ce/developer/create-packages-package-deployer.md
Service: crm-online
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

@nprieto95 Thanks for your feedback. The article clearly mentions the versions of VS that are supported. If you want to raise your idea/suggestion/complaint about the fact that the template does not support VS 2017, please visit https://experience.dynamics.com/ideas/
Closing the issue.

Thank you for your reply. I see that the article mentions the versions that are supported. What I meant, and am suggesting documentation-wise, is to explicitly mention, in a note or with some other style resource, that Visual Studio 2017 is not supported. I know it would be redundant because 2017 is already not present in the supported IDEs list, but I don't think redundancy would harm in this case. To me personally, it would have been more clarifying to have a note that makes it explicit.


[HOLD for payment 2024-12-19] [$250] Missing validate code sent when adding copilot

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.67-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dukenv0307
Slack conversation (hyperlinked to channel name): ts_external_expensify_bugs
Action Performed:

Go to Settings page -> Security page
Click Add Copilot button
Complete the flow
In the final step observe the request validate code modal

Expected Result:
'Code requested. Please check your device.'  is displayed
Actual Result:
'Code requested. Please check your device.'  isn't displayed
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/eda46d4f-1d5b-4867-a11c-3aafa1566282
https://github.com/user-attachments/assets/e2f95403-12c0-4a14-b5bc-b95d54705f5f
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021862155129202940736
Upwork Job ID:<PHONE_NUMBER>202940736
Last Price Increase: 2024-11-28
Automatic offers:

layacat | Contributor | 105162375

Issue OwnerCurrent Issue Owner: @muttmuure

Proposal
Please re-state the problem that we are trying to solve in this issue.
Missing validate code sent when adding copilot
What is the root cause of that problem?
In DelegateMagicCodeModal component, we are setting hasMagicCodeBeenSent based on currentDelegate
But when API ResendValidateCode is called, currentDelegate isn't updated
https://github.com/Expensify/App/blob/0135d4ee1f803622a9ceea894fde62791ceed775/src/pages/settings/Security/AddDelegate/DelegateMagicCodeModal.tsx#L57
What changes do you think we should make in order to solve the problem?

We should update hasMagicCodeBeenSent based on ONYXKEYS.VALIDATE_ACTION_CODE as we did with other validated code modal
    const [validateCodeAction] = useOnyx(ONYXKEYS.VALIDATE_ACTION_CODE);
    ....
    hasMagicCodeBeenSent={!!validateCodeAction?.validateCodeSent}

We can similarly check the places where ValidateCodeActionModal component is used
What alternative solutions did you explore? (Optional)
NA

But if we only update hasMagicCodeBeenSent props by usingvalidateCodeAction?. validateCodeSent, we will never received magic code again in other flows, because the validateCodeSent was not reset

@fedirjh this point is wrong, we still received magic code again in other flows

we should reset the value of validateCodeAction?. validateCodeSent after adding delete (it can be failed or successful) in our optimistic data of addDelegate function:

If we do this then we have to do it with all the places where ValidateCodeActionModal is used in our app

@fedirjh could you please check this comment

@layacat if this happens, we should fix all places right?

Not overdue

Pending payment


Prepare for release v0.5.1

Type of change

Prepare for New Release

Changes
The following changes have been made:

Updates CHANGELOG.md with the changes for this release
Updates README with new version
Updates docs with new version

Checklist

[x] I have linked to any relevant issues.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation where relevant (API docs, the reference, and the Sway book).

[ ] If my change requires substantial documentation changes, I have requested support from the DevRel team

[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.
[x] I have updated the changelog to reflect the changes on this PR.

This PR should wait on https://github.com/FuelLabs/sway-standards/pull/110

Can the changelog for #112 be added as it was missing from the PR itself


Cables, pipes, and logistical transporters are always placed upon right-clicking

If you are holding a cable, pipe, or logistical transporter while opening a door, chest, etc., it is placed in front of the door or chest, rather than allowing you to open said door or chest.
The same goes for any block.
Minecraft version: 1.12.2
Mekanism version: <IP_ADDRESS>6

#BlameAma https://github.com/amadornes/MCMultiPart/issues/73


Add function Context in logger for customization

What was changed

Add a new function Context returning Logger in the Logger interface.

Why?

This helps the logger customization can use the key value pairs which are attached in the context.Context easily.

Checklist

Closes

How was this tested:

Unit test

Any docs updates needed?

Unless I'm misunderstanding the intent, I think this is more clearly done with interceptors. With the recently introduced interceptors, you can intercept calls to GetLogger from workflows and activities via interceptor.WorkflowOutputInterceptor.GetLogger and  interceptor.ActivityOutboundInterceptor.GetLogger respectively and both are passed a context.
You have to wire this up via WorkerInterceptor that returns either/both WorkflowInboundInterceptor and ActivityInboundInterceptor, then in their Init with the given outbound interceptor, call the next in-chain's Init with your own wrapper. I can show an example of this if unclear.

Thanks @cretz
Could you please share some samples to me ?

@tranngoclam - Sure, I will add this as part of https://github.com/temporalio/samples-go/issues/150 soon.

@tranngoclam - Sure, I will add this as part of temporalio/samples-go#150 soon.

Could you give us example how to extract some data from context and include to log message as this example? Our use case is to inject a distributed request/action id to every log message. @cretz

The example has been added.


Ambiguous information for Calling Plan or Direct Routing options

The statement "You need one unassigned phone number for each user that needs to make or receive calls to or from external phone numbers." only, apparently, applies to Calling Plan. With Direct Routing, users do not need a number to make or receive calls to or from external phone numbers. Simply assigning a Caller ID Policy to the user to present the number of a resource account is sufficient.

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

ID: d92b4c9a-d509-7711-a07f-d5c2e1f00665
Version Independent ID: 4316f16a-9e0c-6a24-a9c2-52b8769a7bc4
Content: Create Microsoft 365 users, add Business Voice licenses, and assign phone numbers - Microsoft Teams
Content Source: Teams/business-voice/create-users.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

Hi @JoshPSL, thank you for your feedback.
Yes, this article talks about Business Voice with a calling plan as it is the recommended and most common scenario for small businesses.


about.html

This is a good idea and a replacement for the old README.md

No sorry, I don't see how this extra file would be more useful than the existing documentation.


Proposal to add Kubeapps to package addons.

Signed-off-by: absoludity<EMAIL_ADDRESS>What this PR does / why we need it

Proposes adding the Kubeapps package to the community edition package addons.
Which issue(s) this PR fixes

Fixes: #3732
Describe testing done for PR

The installation of the release is tested during the creation of the package release.
Special notes for your reviewer

I've updated our release script to copy the README.md from the package-for-kubeapps repo, as it is the carvel-specific readme, but it currently is a little bit too specific to the package-for-kubeapps repo. Not sure if we'd be best to update the readme to be appropriate for the package, or create a separate readme with the bulk of that one (all the instructions for install etc.), or whether it's fine as is.

I'm updating the README.md to address the markdown lint, but will need to release a new version, which I'll do soon (just having issues with the bitnami helm repo atm).

...and done.

@vmware-tanzu/tce-owners this PR is just pending your approval. Let me know if we can help you in this process. Thanks!

Thanks @seemiller !


Login with Email Passwordless is not working on Android

After executing the below code, the web3 auth login window opened.
But the window disappears when going to mailbox by tapping the option device button.
So I can't login even though I confirm my email.
The below code works fine on ios but not on android.
const info = await web3auth.login({
  loginProvider: LOGIN_PROVIDER.EMAIL_PASSWORDLESS,
  redirectUrl: resolvedRedirectUrl,
  extraLoginOptions: {
    login_hint: email,
  },
});

Please help me!
https://user-images.githubusercontent.com/51259135/211374476-e816d6ef-9cc0-4a98-8bf8-666d32766b1f.mov

This should be fixed in v4. Pls upgrade


Dependencies on Debian 10

Thanks for this awesome role.
On Debian 10 (buster) I needed to install python3-setuptools to install docker via pip.
To run actual containers, I also needed python3-six.
I suggest to add both as dependencies and install automatically.

Thanks @t2d for reporting this.
Will test and fix.

Hi again,
when using install_recommends: 'no' it seems python3-six might go missing.
But python3-setuptools should not be required.
From testing (molecule test --destroy=never) with python3-six added too the required packages:
~$ lsb_release -d
Description:    Debian GNU/Linux 10 (buster)
~$ ps -fe | grep 8081
busteru+  1043   534  0 23:53 ?        00:00:00 /home/busteruser/bin/rootlesskit-docker-proxy -proto tcp -host-ip <IP_ADDRESS> -host-port 8081 -container-ip <IP_ADDRESS> -container-port 80
busteru+  1048  1043  0 23:53 ?        00:00:00 docker-proxy -container-ip <IP_ADDRESS> -container-port 80 -host-ip <IP_ADDRESS> -host-port 8081 -proto tcp
~$ curl <IP_ADDRESS>:8081

<title>404 Not Found</title>

404 Not Found

nginx

~$ dpkg -l | grep python3
ii  libpython3-stdlib:amd64        3.7.3-1                             amd64        interactive high-level object-oriented language (default python3 version)
ii  libpython3.7-minimal:amd64     3.7.3-2+deb10u3                     amd64        Minimal subset of the Python language (version 3.7)
ii  libpython3.7-stdlib:amd64      3.7.3-2+deb10u3                     amd64        Interactive high-level object-oriented language (standard library, version 3.7)
ii  python3                        3.7.3-1                             amd64        interactive high-level object-oriented language (default python3 version)
ii  python3-apt                    <IP_ADDRESS>                             amd64        Python 3 interface to libapt-pkg
ii  python3-certifi                2018.8.24-1                         all          root certificates for validating SSL certs and verifying TLS hosts (python3)
ii  python3-chardet                3.0.4-3                             all          universal character encoding detector for Python3
ii  python3-debconf                1.5.71                              all          interact with debconf from Python 3
ii  python3-debian                 0.1.35                              all          Python 3 modules to work with Debian-related data formats
ii  python3-debianbts              2.8.2                               all          Python interface to Debian's Bug Tracking System
ii  python3-distutils              3.7.3-1                             all          distutils package for Python 3.x
ii  python3-httplib2               0.11.3-2                            all          comprehensive HTTP client library written for Python3
ii  python3-idna                   2.6-1                               all          Python IDNA2008 (RFC 5891) handling (Python 3)
ii  python3-lib2to3                3.7.3-1                             all          Interactive high-level object-oriented language (2to3, version 3.6)
ii  python3-minimal                3.7.3-1                             amd64        minimal subset of the Python language (default python3 version)
ii  python3-pexpect                4.6.0-1                             all          Python 3 module for automating interactive applications
ii  python3-pip                    18.1-5                              all          Python package installer
ii  python3-pkg-resources          40.8.0-1                            all          Package Discovery and Resource Access using pkg_resources
ii  python3-ptyprocess             0.6.0-1                             all          Run a subprocess in a pseudo terminal from Python 3
ii  python3-pycurl                 <IP_ADDRESS>-0.1                        amd64        Python bindings to libcurl (Python 3)
ii  python3-pysimplesoap           1.16.2-1                            all          simple and lightweight SOAP Library (Python 3)
ii  python3-reportbug              7.5.3~deb10u1                       all          Python modules for interacting with bug tracking systems
ii  python3-requests               2.21.0-1                            all          elegant and simple HTTP library for Python3, built for human beings
ii  python3-six                    1.12.0-1                            all          Python 2 and 3 compatibility library (Python 3 interface)
ii  python3-urllib3                1.24.1-1                            all          HTTP library with thread-safe connection pooling for Python3
ii  python3.7                      3.7.3-2+deb10u3                     amd64        Interactive high-level object-oriented language (version 3.7)
ii  python3.7-minimal              3.7.3-2+deb10u3                     amd64        Minimal subset of the Python language (version 3.7)
~$ pip3 list
Package          Version
---------------- -------------
certifi          2018.8.24
chardet          3.0.4
docker           5.0.0
httplib2         0.11.3
idna             2.6
pexpect          4.6.0
pip              18.1
pycurl           <IP_ADDRESS>
PySimpleSOAP     1.16.2
python-apt       <IP_ADDRESS>
python-debian    0.1.35
python-debianbts 2.8.2
reportbug        7.5.3-deb10u1
requests         2.21.0
six              1.12.0
urllib3          1.24.1
websocket-client 1.1.0

Do you run an old version of ansible? Until 2.8 setuptools doesn't seem to be required (https://docs.ansible.com/ansible/2.8/modules/pip_module.html#notes). But this changed with >=2.9 (https://docs.ansible.com/ansible/2.9/modules/pip_module.html#notes)

The interpreter used by Ansible (see ansible_python_interpreter) requires the setuptools package, regardless of the version of pip set with the executable option.

When testing the following is used:
$ molecule --version
molecule 3.3.4 using python 3.9
    ansible:2.11.1
    delegated:3.3.4 from molecule
    vagrant:0.6.3 from molecule_vagrant


"bazel build //extensions/key_rate_limit:key_rate_limit.wasm" reports an error

Ⅰ. Issue Description
Trying to compile the key_rate_limit plugin in wasm-app reports an error
Ⅱ. Describe what happened
Execute the following command: bazel build //extensions/key_rate_limit:key_rate_limit.wasm
ERROR: /go/src/higress/plugins/wasm-cpp/extensions/key_rate_limit/BUILD:18:15: //extensions/key_rate_limit:_wasm_key_rate_limit.wasm depends on @local_config_cc//:cc-compiler-k8 in repository @local_config_cc which failed to fetch. no such package '@local_config_cc//':
Auto-Configuration Error: Cannot find gcc or CC (clang); either correct your path or set the CC environment variable

After manually setting CC env, but it didn't work
$ echo $CC
gcc
Ⅲ. Describe what you expected to happen
build success, and get .wasm file
Ⅴ. Anything else we need to know?
Ⅵ. Environment:

Higress version:  v1.0.0-rc.4
OS :  Debian GNU/Linux 9
Others:   bazel 5.4.0

Higress uses clang to build Wasm plugins (see here). You need have clang installed first.

Thanks. I'll try.


License

Can you add a license to this repo?
Great work, BTW. I learnt a lot from this repo.

Hello,
All code in this repo is on MIT license, Thanks for the advice I'll add the license file later.


Cannot find module 'h3'

Environment
OS: Linux Fedora 37
Node: v18.15.0
Nitro: 2.3.3
pnpm: 8.2.0
Reproduction

pnpm dlx giget@latest nitro test-app
pnpm dev
open nitro-imports.d.ts

Describe the bug
I am facing an issue with auto-imports. When I use event within eventHandler((event)=>...) is has any type. So when I go to the function definition it takes me to auto-imports and it seems that cannot resolve h3 dep

Additional context
No response
Logs
No response

I suspect you are not hoisting dependencies (which is fine) and so you may need to add h3 to your dependencies.

/cc @antfu For normal pmpm installations (without shamefully-hoist) and non direct deps we might generate full paths in declaration file

Ok, shamefully-hoist=true fixed it ;)

btw I am getting the same for node:http when I want to figure out what I can call on event.node.res object

You will probably need to install @types/node.

That's right :+1: I just think it would be nice that it works out of the box :)


Gulpfile.js - Not generating template javascript's properly

gulp tasks tpl:dropdown, tpl:search-filter, tpl:tabs not generating template javascript's properly. Template file dropdown_template.js don;t have any template names in it a.put(' ',
Any one faced this same issue?
angular.module("lumx.dropdown").run(['$templateCache', function(a) { a.put('', '

\n' +
    '');
	a.put('', '

\n' +
    '');
	a.put('', '
\n' +
    '

\n' +
    '
\n' +
    '');
	 }]);

I just tried two of the three tasks you mentionned and I don't have this problem... Did you change the gulpfile ? Could you check which version of gulp-templatecache is used in your repo ?

No i didn't change anything on gulp file.
gulp version - 3.8.11
gulp-templatecache - 0.0.3
Node.js - 0.10.35

Looks really weird. I run it  with the same config as yours and I don't have this problem... On which OS do you work ? It's awkward because you have the right content in the cached template...

Yes it is so wierd. I'm using windows 7 OS. Also i noticed in few places we are renaming the path /demo to ' ' and /js to ' '. If i don't change /demo to \demo, it is not renaming the directory.

Have you tried to use gulp-templatecache besides this project ? I work on Mac, it may come from the platform. Could make a test project and use gulp-templatecache ?
Where did you find the renaming you mentionned ?


:fire: add support for figure dict input + propagate _grid_str

This PR does;

[x] support figure as a dict as input for our wrappers (e.g. FigureResampler(fig.to_dict()) with fig a go.Figure)
=> this is in line with the vanilla plotly behavior (see BaseFigure constructor documentation)
[x] propagate _grid_str in our composable constructors
[x] test the above

Codecov Report

Merging #92 (862bc0a) into main (2ed7423) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #92      +/-   ##
==========================================
+ Coverage   98.12%   98.15%   +0.03%
==========================================
  Files          10       10
  Lines         746      759      +13
==========================================
+ Hits          732      745      +13
  Misses         14       14

Impacted Files
Coverage Δ

...tly_resampler/figure_resampler/figure_resampler.py
90.90% <100.00%> (+0.90%)
:arrow_up:

...ler/figure_resampler/figure_resampler_interface.py
99.70% <100.00%> (+<0.01%)
:arrow_up:

...sampler/figure_resampler/figurewidget_resampler.py
99.00% <100.00%> (+0.06%)
: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 2ed7423...862bc0a. Read the comment docs.


Pretrained Big Sleep

When I run !dream "something" on the given colab, it seems to start the training process and displays epochs / losses. Is there a way to simply look at the output of the model using pretrained weights and instead of retraining everything from scratch?

There's no single pretrained network here to make images from text. There's BigGAN to make images and CLIP to evaluate how an image matches a given text. Therefore one has to iterate to find an image which matches the prompt, that's why you are seeing epochs and losses. The loss measures how well the current image matches the text, and the goal is to minimise it. The models are not being trained at all.

Just a quick related question: how much loss is to be considered good enough, on average with big-sleep? I mean I am seeing that around -36 any further progress becomes really hard... so is that considered a good loss amount? Or are you seeing different results?


Getting internal server error while running flask app on default route http://<IP_ADDRESS>:5000/

application.py
`import os
from flask import Flask, render_template, request
from sqlalchemy import create_engine
from sqlalchemy.orm import scoped_session, sessionmaker
app = Flask(name)
engine = create_engine("postgresql://postgres:123@localhost:5432/lecture3")
db=scoped_session(sessionmaker(bind=engine))
@app.route("/")
def index():
flights =  db.execute("SELECT * FROM flights").fetchall()
return render_template("index.html", flights=flights)
@app.route("/book", methods=["POST"])
def book():
"Book a flight."
name = request.form.get()

if name == 'main':
app.run()
`

this is not related to this repo